|
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
|
|
| Performance |
| Author |
Message |
| bman |
| |
| Group | : Members |
| Posts | : 2 |
| Joined | : 2007-12-05 |
|
| Profile |
|
| Posted : 2007-12-06 01:17:44 |
Hello,
I'm trying to figure out why simple queries are taking so long. I have searched the forum and made changes to the DSN .. but i don't seem to notice any difference. I'm using the trial version v8 with QB 2006 premiere.. a fresh company database and a simple query: select name from customer
There's only 1 customer in the table and it is taking about 10 seconds to return the results. I've tried making optimizer changes, chunk size changes, iterator changes, QB open, QB closed, multi-user, single-user..
Is this a limitation of the qodbc trial?
Thanks,
Brian |
|
|
|
| Tom |
 |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2007-12-06 10:06:21 |
Basically QODBC is spending most of the 10 seconds checking that you haven't added new customers. Try running:
Select * from Customer NOSYNC
for the 2 second answer. |
|
|
|
| bman |
| |
| Group | : Members |
| Posts | : 2 |
| Joined | : 2007-12-05 |
|
| Profile |
|
| Posted : 2007-12-06 15:26:19 |
Hi Tom,
Not much of a change. Is there a best practice as far as keeping QB open or closed... single or multi-user..
It might be 1-2 seconds faster... The application that I need to write to use QODBC doesn't really care about 'up to date' data.. so whatever gets me
the quickest result is the goal
Thanks
Brian |
|
|
|
| Tom |
| |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2007-12-06 18:28:15 |
| The best practice is to keep QuickBooks and the company file open on your desktop.... mine has been running for months. A first time connect will take longer, run the select statement four times and you will see the answer in less than 1 second. |
|
|
|
|
|
| Posted : 2008-01-17 06:49:15 |
| I'm pulling transaction lists into SQL Server 2005 nightly. Typically tens of thousands of records that takes 2+ hours to run. Thinking about changing backend from QBPro 2005 to QBES 2008. Do you think this will speed up query performance dramatically? Should the change from the C-Index database to Sybase iAnywhere database make a big difference here? |
|
|
|
| Tom |
| |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2008-01-17 08:05:51 |
| Yes, upgrading from QuickBooks Pro to QuickBooks Enterprise does provide better performance in larger company files. |
|
|
|
|