Performance of OleDB Vs. ADO.NET

[Arsalan Ahmad]

Hi,

I am developing an ASP.NET website using MySQL as a backend database.
Database access consists of simple update, select and insert queries however
its likely that there will be a number of users simultaneously accessing the
database. I can access database using either ADO.NET or using OleDB(OleDB
APIs can be used as COM objects can be used in .NET easily). However, which
method is preferable in terms of performance? using ADO.NET or using OleDB
COM objects? (Overall performance could be separated into performance during
connection (which one has less overhead in connection), performance for a
select (which one has less over head for select) and performance for
update/insert/delete (which one has less overhead). I am particularly
interested in performace for MySQL database however for any general database
is also appreciable.

Also could any one please tell me is OleDbConnection class is part of
ADO.NET or separate and how can we compare its performance with OleDB COM
APIs (and with ADO.NET if it is separate from ADO.NET)?

Are there any performance benchmarks for above?

Thanks,

Arsalan

 

[Cor Ligthert [MVP]]

Arsalan,

With ADO.NET you can use the special provider of the DataBase (as there is
for MySQL), plus OleDB and ODBC.

With .Net you can use beside that interop to COM

Normally as best is used the sequence that I have used.

I hope this helps,

Cor

 

[Fred Exley]

..

Arsalan,

With ADO.NET you can use the special provider of the DataBase (as there is
for MySQL), plus OleDB and ODBC.

With .Net you can use beside that interop to COM

Normally as best is used the sequence that I have used.

I hope this helps,

Cor