Member Login

Username
Password
Forget Password
New Sign Up
Search Forum

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

Forum : performance issuesSearch Forum

Forum Home > QODBC - ODBC Driver for QuickBooks > QODBC v6 Forum

 New Topic 
 
 Post Reply 
[1]  
 performance issues 
 Author   Message 
  merlin 
  
 Group: Members 
 Posts: 1 
 Joined: 2006-07-29 
 Profile
 Posted : 2006-07-29 03:28:22
we are evaluating the qodbc driver.  we are having performance issues pulling data from our relatively small quickbooks file.  We appear not to be getting any help from the optimizer...I confirmed this by monitoring the network traffic.  Queries from both the provided vb app and the vbscript transfer mechanism run the same speed regardless if the optimizer is on/off or how the query is written.  I tried the various techiniques listed in the forums, reset the cache, etc.

For example, a simple vbscript which loads our test quickbooks database (select * from customer) and prints the company name takes about 5 minutes for ~ 500 records.  I'm the limitations of the qb backend but as i understand it there is a sqlite backed local cache.  If this is working properly I think performance should be acceptable.  Is there anything else to try? 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2006-07-29 09:45:41

With the release of QODBC v6.00.00.155 (and later) we had to do a little more checking for deleted transactions and payments so tables that reference a open balance now run slower. Most users tend to use queries like:

SELECT * from Customer

which will run slowly as QODBC has to display the correct current balance for each customer, while this will run much faster:

SELECT "Name","LastName","FirstName","BillAddressAddr1",
"BillAddressAddr2","BillAddressCity",
"BillAddressState","BillAddressPostalcode"
from Customer

However can also override your QODBC Optimizer configuration screen settings to suit what you are actually doing by using the following tags:

VERIFIED | VERIFY - Forces Full Resync with QuickBooks on the optimized table before Query starts
CALLDIRECT | UNOPTIMIZED - Passthru query directly to QuickBooks - use no optimizations
OPTIMIZE | OPTIMIZED | NOSYNC - Passthru query to optimized table directly for maximum speed

For example:

SELECT * from Customer NOSYNC

will run very fast as it uses our sqlite backend ................

See: How do I setup the QODBC Optimizer? Where are the Optimizer options? for more information on the QODBC Optimizer.

 

  Top 
 New Topic 
 
 Post Reply 
[1]  

Jump to