|
Let me qualify by saying that I am NOT an ODBC expert. First, Eric has some good points. Run your statement in debug natively to see what, if anything can be done there to improve performance. If that doesn't point it out, and your statement is rather complex post it, and we'll see if the structure may be the issue. I've heard that ODBC can be a bit of a pig. I know that there is a little competition in the ODBC driver market. A different one may solve your problem. Paying for one might even be considered. May still be cheaper than a hardware upgrade. I've heard of people using alternatives to ODBC. Buzzwords like JDBC or OLE/DB come to mind. I've also heard that instead of ODBC that one may consider using Stored Procedures. Let the SQL run on the server and pass back result sets. This isn't really rocket science. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
