Wrox Programmer Forums
Go Back   Wrox Programmer Forums > .NET > Other .NET > ADO.NET
| Search | Today's Posts | Mark Forums Read
ADO.NET For discussion about ADO.NET.  Topics such as question regarding the System.Data namespace are appropriate.  Questions specific to a particular application should be posted in a forum specific to the application .
Welcome to the p2p.wrox.com Forums.

You are currently viewing the ADO.NET section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old July 30th, 2004, 10:03 AM
Registered User
 
Join Date: Jul 2004
Location: , , .
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default Ado.net performance question (SQL server vs OleDB

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


 
Old August 2nd, 2004, 10:37 AM
Authorized User
 
Join Date: Aug 2004
Location: , , .
Posts: 32
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via Yahoo to humour
Default

Let me paraphrase from the WROX publication: "ASP.NET Databases using VB.NET isbn: 1-86100-619-5.

The SQL server .net data provider is highly optimized for SQL SERVER 7 and above. The OLE DB .NET DB provider will work but will NOT perform as well. That being said I do see your point. Perhaps your application doesn't require the absolute most optimized speed.

Hope this helps.




Similar Threads
Thread Thread Starter Forum Replies Last Post
ADO.NET connectivity problem with SQL Server !!! virajp ADO.NET 2 December 5th, 2005 11:51 PM
SQL Server with ADO.NET dounme SQL Server 2000 4 February 8th, 2005 09:19 PM
ADO.Net slower than SQL Server Query Analyzer s5g5r ADO.NET 1 January 26th, 2005 09:49 PM
how can i link to sql-server with ado.net[B)] zjxgjp ADO.NET 1 December 25th, 2004 09:50 AM
using oledb to retrieve data from sql server w A2K nikesierra2306 Access VBA 0 October 20th, 2004 04:36 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.