RE: ODBC Perfomance issue

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

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
>
> ------------