|
Buy Support
Incidents |
|
If you can't find your answer
in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us
private or confidential information: |
|
Click Here
|
If you can't
login and post questions or you are having trouble viewing forum posts:
Click Here
|
Callback
Support |
|
If you live in USA, UK, Canada, Australia or New
Zealand, you can leave us details on your question and request us to call you back and discuss
them with you personally (charges apply). |
|
Click Here
|
Buy Support
Incidents |
|
If you can't find your answer
in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us
private or confidential information: |
|
Click Here
|
|
| TimeTracking Query Problems |
| Author |
Message |
|
|
| Posted : 2008-01-31 02:56:18 |
I have a few problems when querying the TimeTracking table
- Query takes around 10 min to report any rows, filtering has no noticible effect, currently querying SELECT * FROM TimeTracking WHERE ( TxnDate > {d'2006-12-31})
- I've been unable to do this test query with microsoft query, and the VBDemo only returns 10000 records. I'll be bringing data into excel to process, and need to get all possible returns, is this a limitation in the vbdemo, or am I missing something?
To explain, I'm probably going to have to process somewhere in the range of 30-36thousand records for any given report, I'm hoping that I'll not have to do multiple querys, with multiple filtering sets, especially if each query will tie up 10min plus. Of course any help will be greatly appreciated.
Thanks,
Icabod |
|
|
|
| Tom |
 |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2008-01-31 09:49:32 |
VB Demo does have a limitation on the number of rows returned. Using MS Query you will get the full rowset. I suggest you bump your Iterator or Chunk Size setting to 5,000, but no larger than 20,000.
|
|
|
|
|