Re: Sybase ASA .NET provider vs. ODBC by Cowboy
Cowboy
Thu Aug 19 19:26:02 CDT 2004
If you can do all of your database work in OLEDB, I would use it over ODBC,
as ODBC is slower (lots of reasons, not enough time).
I have not tried the Sybase provider, but much of the data access, outside
of SQL Server will ultimately end up with some Interop somewhere down the
line. How they actually make the connect is important. If the driver is the
only COM, you might not have a serious problem. If they simply wrapped their
entire stack, you might.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
************************************************
Think Outside the Box!
************************************************
"Evan Stone" <evan_stone_n0spaam@intuit_n0spaam.com> wrote in message
news:u8$kOgjhEHA.556@TK2MSFTNGP10.phx.gbl...
> Has anyone here done any benchmarking with the iAnywhere.Data.AsaClient
> provider versus using System.Data.Odbc (or Oledb for that matter)?
>
> Initially I thought that the iAnywhere provider was going to be the
> better way to go, but in learning that it's just a .NET dll layer
> (iAnywhere.Data.AsaClient.dll) over a Win32 DLL (dbdata9.dll), I was
> just wondering how much it would buy us.
>
> <thinking_out_loud>
> Additionally, it seems that if we want to use other databases (like
> SQLServer, for instance), then our best bet for compatibility is to use
> the ODBC provider (and use T-SQL).
> </thinking_out_loud>
>
> Does this all sound reasonable, or am I way off base here?
>
> Thanks!
>
> -Evan