Re: Ado.net performance question (SQL server vs OleDB data provider)

From: Jonathan Allen (X_at_X)
Date: 08/04/04


Date: Wed, 4 Aug 2004 15:33:28 -0700

I have a Database class that takes a SQL Statement and returns an
IDataReader. All the possible exceptions are caught in the Database class
and wrapped in my own exception type.

-- 
Jonathan Allen
"Mike via .NET 247" <anonymous@dotnet247.com> wrote in message
news:OsYF6$heEHA.1652@TK2MSFTNGP10.phx.gbl...
Hi,
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
-----------------------
Posted by a user from .NET 247 (http://www.dotnet247.com/)
<Id>IpXE03/1GEyoZ1aRkgRsKQ==</Id>


Relevant Pages

  • Re: VS.net installs sql express as default datastore for role/membersh
    ... I can use sql or access databases for dataaccess, ... Asp.net web site administration tool. ... Select provider configuration ... it seems easy to select an other database. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: dbdebunk Quote of Week comment
    ... > a lot of really bad SQL programmers. ... But SQL does not have a pointer data type or the ... > being told to design a database. ... But why is little Cindy Lou Who employee ...
    (comp.databases.theory)
  • Re: application design problem
    ... Actual action is depends on your Provider which provide service for a particual database or data store. ... When I would click Button1 this sql would execute: ... I dont think its a good idea to put all your client spcific logic ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: DBMS and lisp, etc.
    ... Naively implemented with SQL, again for 10 ... (1 query for the initial orders, 1 query for each order for its ... soon as you upgrade to the SQL database. ... (eq (order-customer orderA) ...
    (comp.lang.lisp)
  • Re: dbdebunk Quote of Week comment
    ... > a lot of really bad SQL programmers. ... a surrogate key should support the primary key. ... But SQL does not have a pointer data type or the ... > being told to design a database. ...
    (comp.databases.theory)