Search code examples
.netdatabaseodbcoledbsqlclient

When should I be using Odbc, OleDb, SQLClient? What are the trade-offs

I am starting off with a SQLServer database. So it would seem that I should use System.Data.SqlClient namespace. But, there is a chance that we might shut down our SqlServer database and go to MySql or Oracle. For this reason, I am coming up with a set of standards on how our .Net apps will communicate with the database, so as to make it easier to migrate to a different database system in the future if we needed to do so.

So here are the standards:

  1. Use an ORM if possible (eg NHibernate) (No LINQ as it only supports SqlServer, but what about Entity framework and its support for Oracle and MySql?)
  2. If ORM is an over-kill, then use parameterized SQL queries.
  3. Use stored procedures only for long running or complex actions that need to be performed on the database.

Which brings me to my main question at hand. Which namespace should I be using to code my DAL?

It looks to me that the choice is between System.Data.ODBC and System.Data.OleDB:

  • What are the trade-offs?
  • Is one preferred over the other?
  • What are your thoughts about the first 3 standards?
Solution

  • System.Data.SQLClient

    Connects to SQL Server 2000 and later only, but you will get optimal performance when connecting to those databases.

    System.Data.OledbClient

    Connects to SQL 6.5

    OLEDBClient gives you ability to connect to other database like ORACLE or Access. But for working with SQL Server you will get better performance using SQLClient.

    Note: For connecting to ORACLE, Microsoft also has ORACLEClient.

    System.Data.ODBCClient

    Connects to legacy databases only, using ODBC drivers. (E.g. MS Access 97.)

    Original source