|
Home > Archive > Sybase Open Client > March 2005 > OC - Native Driver vs ODBC ?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
OC - Native Driver vs ODBC ?
|
|
| Tjohanse 2005-03-30, 7:09 pm |
|
I got a question from a consultant in house, he ask "What is
the "Native Driver" for ASE and IQ called in Sybase" ?
Is there any bennefit of using "native driver" or why would
you not use "native drivers" ?
Would native driver be to prefer, instead of ODBC ?
| |
|
| Hi -
I am not sure what you refer to exactly. For ASE Sybase provides ASE
ADO.NET Data Provider, a native ADO.NET Provider that uses the MS .NET
Framework to build various applications. The ASE ODBC Driver (both OEM and
the Sybase built) use the TDS layer directly, that is, they no longer
require the use of Sybase Open CLient to communicate to the ASE server.
This starts with the 12.5.X releases (Sybase built started with OCS SDK EBF
12117.
There is also the OLE DB Provider (both OEM and Sybase built) which also
uses the tds layer directly (TDS is the communicating protocol that clients
use the connect/communicate to the ASE)
pv
<Tjohanse> wrote in message news:42149850.20de.1681692777@sybase.com...
>
> I got a question from a consultant in house, he ask "What is
> the "Native Driver" for ASE and IQ called in Sybase" ?
>
> Is there any bennefit of using "native driver" or why would
> you not use "native drivers" ?
>
> Would native driver be to prefer, instead of ODBC ?
|
|
|
|
|