Re: Performance of OleDB Vs. ADO.NET

Tech-Archive recommends: Fix windows errors by optimizing your registry

You are always going to have more overhead with COM interop in .NET.
Use ADO.NET with the OleDb provider for the best performance (and
fewest problems).

--Mary

On Mon, 27 Mar 2006 20:55:43 +0200, "Arsalan Ahmad"
<arsal__@xxxxxxxxxxx> wrote:

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

.

Relevant Pages

  • Re: ASP --> OLEDB --> Access db ?
    ... The directory where the database resides should have change or modify ... OLEDB, which is what you're referring to. ... have to use FTP to put the files there if you're publishing using FPSE ... without even the implied warranty of merchantability ...
    (microsoft.public.inetserver.asp.db)
  • Re: Wanted:MAIL.MAI structure definition
    ... a relational database is more flexible in the retrival of data. ... Perhaps this impact has been softened as hardware has gotten faster, but, overhead is overhead, and if you weren't using the advances in hardware for overhead, those designs that have less overhead would also gain from the faster hardware. ... RFC822 header because your XML parser wouldn't be able to understand new ...
    (comp.os.vms)
  • Re: Newbie - general question about ADO.NET
    ... Sure, it carries some overhead, but worrying about the minor amount ... If a database is localy on PC - ... ADO.NET is connectionless, but I don't care about connection, ... >>> because the database is located on PocketPC. ...
    (microsoft.public.pocketpc.developer)
  • ~Re: data access
    ... Instead of a DSN that uses old ODBC technology, ... You can get your OLEDB connection string at ... drive directory using no system database. ...
    (microsoft.public.inetserver.asp.general)
  • Re: Which database support?
    ... it presumes that the user is apparently interacting with the database through ... >>ADO is likely the better way to go, although ODBC is a close second. ... >>ADO is built on OLEDB; Both are based on a set of interfaces defined by ...
    (microsoft.public.vc.mfc)