× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. January 2003

RE: ODBC Perfomance issue

That is my experience, as well. ODBC via ADO is another layer. Direct API calls would be faster, but prone to error and other problems.

I also have seen that IBM's OLE/DB driver is lacking in some functionality. It used to allow only 1 result set, where Hit's driver allowed multiple. That is why we went with the MS ODBC driver via ADO, which does allow multiple result sets and could use IBM's ODBC driver - not a good solution, IMO, but it had no additional cost.

AFAIK, both OLE/DB and ODBC drivers from IBM use the Database host servers -QZDASOINIT, etc.

Vern

At 09:30 AM 1/30/2003 -0500, you wrote:
>Oliver, ODBC may not have been the culprit. What kind of data access was
>the VB application using, DAO, RDO, or direct calls to the ODBC API?

True. HOWEVER, it's been my experience too that OLEDB via ADO is noticably
faster than ODBC via ADO. It's also been my experience that the 3rd party
OLEDB drivers (Hit's for examples) outperform IBMs.

-Walden

------------

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.