ODBC vs Ole Db

  • Thread starter Thread starter Todd
  • Start date Start date
T

Todd

My client is using a Sybase database. Should I use ODBC
or Ole Db with ADO.NET?

Thanks,
Todd
 
Hi Todd,

Whichever suits you best.
I guess odbc one should be a bit faster.
Can't comment on differences between them though.
 
OK, so other than speed no big advantages either way.
ODBC is it! Thank you for your post.

Todd
-----Original Message-----
Hi Todd,

Whichever suits you best.
I guess odbc one should be a bit faster.
Can't comment on differences between them though.

--
Miha Markic [MVP C#] - RightHand .NET consulting & software development
miha at rthand com
www.rthand.com

Todd said:
My client is using a Sybase database. Should I use ODBC
or Ole Db with ADO.NET?

Thanks,
Todd
Click to expand...


.
Click to expand...
 
It's a function of functionality as much as performance. The Odbc .NET Data
Provider is a "managed" provider while the OleDb provider is not (relies on
COM). However, the Sybase ODBC driver might not be as competent as the
Sybase OLE DB provider--just as the JET ODBC driver is a subset of the JET
OLE DB provider functionality. I suggest going to the Sybase site and seeing
what they recommend.

hth

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________

Miha Markic said:
Hi Todd,

Whichever suits you best.
I guess odbc one should be a bit faster.
Can't comment on differences between them though.

--
Miha Markic [MVP C#] - RightHand .NET consulting & software development
miha at rthand com
www.rthand.com

Todd said:
My client is using a Sybase database. Should I use ODBC
or Ole Db with ADO.NET?

Thanks,
Todd
Click to expand...
Click to expand...
 
Hi Bill,

William (Bill) Vaughn said:
It's a function of functionality as much as performance. The Odbc .NET Data
Provider is a "managed" provider while the OleDb provider is not (relies on
COM).
Click to expand...

It is a thin line though.
One relies on set of api while the other communicates through com.
I wouldn't say that the later is not a managed provider since both are only
wrappers.
 
I didn't label them, the dev team at Microsoft did. My (informal) tests show
a dramatic (20%) difference in performance (Odbc over OleDb) when accessing
SQL Server. The SqlClient provider is even faster (once connected).


--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
 
Hi Bill,

William (Bill) Vaughn said:
I didn't label them, the dev team at Microsoft did.
Click to expand...

I wonder what was the rationale behind.

My (informal) tests show
a dramatic (20%) difference in performance (Odbc over OleDb) when accessing
SQL Server.
Click to expand...

Interesting. Big boost indeed.

The SqlClient provider is even faster (once connected).

That was expected :)
 
Back
Top