469,945 Members | 2,262 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,945 developers. It's quick & easy.

Performance - ODBC vs OLEDB vs SQL Providers

I've come from a strong ODBC usage background (using DSN's on servers) and
am wondering whether I should start recommending OLEDB or SQL data providers
rather than ODBC

It seems that ODBC support was only provided in the .NET Framework Ver 1.1 -
should I be thinking ODBC as "old" legacy data provisioning or still keep
using it ?

..NET Applications on my plate may need to use MS SQL Server or Oracle
databases.

Anyone got any comments on this ?

- peteZ
Nov 15 '05 #1
4 12973
I'd definitely vote for the managed SQL provider for the MS SQL server
connectivity because it is completely managed implementation that does not
use neither ODBC nor OLEDB underneath.

--
Dmitriy Lapshin [C# / .NET MVP]
X-Unity Test Studio
http://x-unity.miik.com.ua/teststudio.aspx
Bring the power of unit testing to VS .NET IDE

"PeteZ" <pe***@aol.com> wrote in message
news:%2***************@TK2MSFTNGP10.phx.gbl...
I've come from a strong ODBC usage background (using DSN's on servers) and
am wondering whether I should start recommending OLEDB or SQL data providers rather than ODBC

It seems that ODBC support was only provided in the .NET Framework Ver 1.1 - should I be thinking ODBC as "old" legacy data provisioning or still keep
using it ?

.NET Applications on my plate may need to use MS SQL Server or Oracle
databases.

Anyone got any comments on this ?

- peteZ


Nov 15 '05 #2
bob
managed SQL providers in should offer improved performance..
Dmitriy Lapshin [C# / .NET MVP] wrote:
I'd definitely vote for the managed SQL provider for the MS SQL server
connectivity because it is completely managed implementation that does not
use neither ODBC nor OLEDB underneath.


Nov 15 '05 #3
Second and thrided. I dont have any actual figures to hand but I have
benchmarked this in the past and they are FAR faster. If needs be try and
create a middleware layer to your app that takes the data interfaces
(IDataReader etc.) to do your business logic, that way you can create
another layer beneath that that sets up your connection etc. that is db
specific.

HTH
Kieran

"bob" <us**@example.net> wrote in message
news:bP*****************@news02.tsnz.net...
managed SQL providers in should offer improved performance..
Dmitriy Lapshin [C# / .NET MVP] wrote:
I'd definitely vote for the managed SQL provider for the MS SQL server
connectivity because it is completely managed implementation that does not use neither ODBC nor OLEDB underneath.

Nov 15 '05 #4
> It seems that ODBC support was only provided in the .NET Framework Ver
1.1 -
should I be thinking ODBC as "old" legacy data provisioning or still keep
using it ? .NET Applications on my plate may need to use MS SQL Server or Oracle
databases.


You can use the .Net ODBC Provider also with .Net framework 1.0, but you
have to download and install it separately, it was not on time to include it
in VS.Net 2002.

Said that, it is recommended to use the managed .Net data providers for
Oracle and SQL Server. If you are interested in database interoperability,
take a look at the IDBXXX interfaces (IDBConnection instead of
OracleConnection, SQLConnection). Notice also that parameter markers and
ODBC syntax may not be supported.

HTH,

Carlos Quintero

Nov 15 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by Dr. Indera | last post: by
6 posts views Thread by serge calderara | last post: by
5 posts views Thread by lastusernameleft | last post: by
4 posts views Thread by Andreas Lauffer | last post: by
1 post views Thread by redefined.horizons | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.