ADO performance

From: "=?Utf-8?B?U3BhbXA=?=" <Spamp@xxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: ADO.Net Performance
Date: Wed, 28 Jul 2004 12:48:05 -0700
Newsgroups: microsoft.public.dotnet.datatools

Hi,

I have a general question. I haven't had an opportunity to benchmark the
Sql database provider classes vs. the OleDb database provider classes. My
application could be connecting to a SQLServer, Oracle, or an Access
database. I have read that there are performance gains using the SQL
Server provider classes when communicating with a SQLServer database. My
application will only be performing SQL commands such as Update, Insert,
and Delete. It will not be using and DataSets or DataReaders. I'm
wondering if there is a performance gain using the database specific
providers as opposed to the OleDB provider since the application will only
be performing commands that do not return data. I assume that the SQL
command is passed to the Data provider is then sent to the database where
all the real work is done and presumable most of the time is spent. Anyone
know if this is an accurate assumption. I would rather use the OleDB
providers because it is easier to support the multiple (Oracle, SQLServer,
and Access) databases. I know I could create a class factory that created
the appropriate kind of database provider and returned the IDbConnection or
IDbCommand objects but the exception handling makes the code messy since
the exceptions are database specific (SqlException, OleDbException, and
OracleException). Each location in the code would require three different
exception handlers which isn't very well easy to maintain.

Any comments or suggestions?

Thanks,
Mike

ADS

.

Relevant Pages

  • Re: ADO connection with VBS to locally stored MS-Access database
    ... Even using of the OLEDB Jet provider is better, I do not see any confusion ... You could use ODBC or OLEDB syntax but in this case ADO will using ... > I am trying to connect to a local Access database via ADO and VB Script. ...
    (microsoft.public.data.ado)
  • Re: .NET data provider or OLEDB provider?
    ... I don't see where you see a built-in query engine. ... There are third party tools that provider SQL parsing IIRC, ... >> database) is that the .NET model doesn't support scrollable, ...
    (microsoft.public.data.oledb)
  • Re: DMX cmd cant see Access db
    ... into a SQL database - primarily to work around the issues you are running ... SQL Server Data Mining ... provider I'm trying to use in order to read data from an Access ... Dejan Sarka, SQL Server MVP ...
    (microsoft.public.sqlserver.datamining)
  • Re: DataBase Programming
    ... If I write an application using an SQL database, ... Can I use ADO.Net with the OLEDB Class for SQL databases? ... downloadable and fit inside SQL server pack 3. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Help with Building SQL for MSACCESS Data Layer
    ... You get one finished and then find that the other database is from ... lines of code (the + is for additional params). ... Oracle param starts to match the @Param format of SQL Server. ... > The first is that they use different dotnet object SQLClient and OLEDB. ...
    (microsoft.public.dotnet.framework.adonet)
Loading