Microsoft SQL Server OLEDB Provider Deprecation Announcement
The commercial release of Microsoft SQL Server, codename “Denali,” will be the last release to support OLE DB. Support details for the release version of SQL Server “Denali” will be made available within 90 days of release to manufacturing. For more information on Microsoft Support Lifecycle Policies for Microsoft Business and Developer products, please see Microsoft Support Lifecycle Policy FAQ. This deprecation applies to the Microsoft SQL Server OLE DB provider only. Other OLE DB providers as well as the OLE DB standard will continue to be supported until explicitly announced.
It’s important to notice that this announcement does not affect ADO’s and ADO.NET’s roadmaps. In addition, while Managed OLEDB classes will continue to be supported, if you are using it to connect to SQL Server through the SNAC OLEDB Provider, you will be impacted.
If you use SQL Server as your RDBMS, we encourage you to use SqlClient as your .NET Provider. In case you use other database technologies, we would recommend that you adopt their native .NET Providers or Managed ODBC in the development of new and future versions of your applications. You don’t need to change your existing applications using OLE DB, as they will continue to be supported, but you may want to consider migrating them as a part of your future roadmap. Microsoft
is fully committed to making this transition as smooth and easy as possible. In order to prepare and help our developer community, we will be providing assistance throughout this process. This will include providing guidance via technical documentation as well as tools to jump start the migration process and being available right away to answer questions on the SQL Server Data Access forum.
Luiz Santos
ADO.NET Program Manager
Comments
Anonymous
November 23, 2011
Thanks for post such as very useful and very lovely post..... <a href="www.amperesoftware.com/"> .NET Application Development :</a> - Ampere has extensive exposure and experience in Migrating Java applications to.NET Framework, Microsoft.net Development, .NET 3.5 Application Development, NET 2.0 Application Development, Maintaining .Net Application, Migrating Legacy Application to Latest .NET Framework etc…Anonymous
January 11, 2012
Can we please talk about version numbers vs code names, OR, supply the list that puts codename with v num. Denali is ... SQL 2010???Anonymous
December 08, 2012
Hi Luiz, Do you know if that is the same for SSIS? I posted on msdn forum 5 questions. You input would be appreciated social.msdn.microsoft.com/.../92390f70-e17d-4f9f-9965-97746f3f7dc8 Many thanks EmilAnonymous
February 04, 2014
This is going to affect lot of clients dependent on OLEDB. I am wondering how Microsoft can bluntly do harm to it's own product users? MS Office applications that depend on SQL server -VBA connectivity through OLEDB can no more have latest OLEDB provider to work with ADO.