Deprecation of OLEDB -> ODBC RRS feed

  • Question

  • also posted here with more details (especially question 3 for this forum)

    1. To experience the least pain (or no pain) in the future as OLEDB is phased out and ODBC is used, should we be using System.Data.SqlClient, System.Data.ODBC, or something else for new db development.

    2. How exactly do we use “SQL Server Native Client driver with System.Data.Odbc”?

    3. Can the ADO.Net Entity framework be used for new development, without having to make future code changes due to the drop of OLEDB for SQL Server? i.e. it will seemlessly and transparently transition in the background.

    Friday, September 2, 2011 3:30 PM


  • Hi,

    Try All the .NET providers are inheriting from common DbXXX classes. As you posted  in EF you likely noted that the connection string and the actual underlying provider are specified in a config file, EF using likely what you find at the link I gave to instantiate whatever provider you configured.

    Please always mark whatever response solved your issue so that the thread is properly marked as "Answered".
    Friday, September 2, 2011 7:35 PM