As long as you can find providers for each database, OLEDB is faster than
ODBC. ODBC has more options, but I believe you can find providers for all of
the databases you have listed (have not tried Ingres personally; there is an
open source driver for MySql, however).

Signature
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
*************************************************
Think outside of the box!
*************************************************
> Hi,
>
[quoted text clipped - 10 lines]
>
> Chris
Chris - 19 Sep 2006 00:08 GMT
Hi,
Thanks for the reply, but do you know if there is a document where they
compare response times etc?
Regards
Chris
> As long as you can find providers for each database, OLEDB is faster than
> ODBC. ODBC has more options, but I believe you can find providers for all
[quoted text clipped - 15 lines]
>>
>> Chris
Shawn Wildermuth (C# MVP) - 19 Sep 2006 02:11 GMT
Hello Chris,
Generally OLE DB is preferrable because it can retrieve data a bit more efficiently
than ODBC...*but* it all depends on the quality of the driver/provider. It
is not difficult to write a badly performing OLE DB provider that is slower
than its ODBC counterpart. In general you will also find that the Managed
Providers (ADO.NET) for SQL Server and Oracle will out perform their OLE
DB/ODBC because of marshaling issues.
I know its a lot of opinion without a lot of data, but there are so many
things that can impact performance, usually the provider of the data is just
one of a number of possible cause of performance issues.
Thanks,
Shawn Wildermuth
Speaker, Author and C# MVP
http://adoguy.com
> Hi,
>
[quoted text clipped - 29 lines]
>>>
>>> Chris
Max - 19 Sep 2006 11:36 GMT
There is also a managed MySQL Data provider that works very well.
> Hello Chris,
>
[quoted text clipped - 46 lines]
>>>>
>>>> Chris