The SQL Server team announced that Microsoft is aligning with ODBC for native relational data access – the de-facto industry standard.
“This move supports our commitment to interoperability and our partners and customers’ journey to the cloud. SQL Azure is already aligned with ODBC today,” stated Rohan Lam, Program Manager – SQL Server Connectivity.
Lam writes that “The next release of Microsoft SQL Server, Code Name “Denali,” will be the last release to support OLE DB. OLE DB will be supported for 7 years from launch, the life of SQL Server Code Name “Denali” support, to allow you a large window of opportunity for change before deprecation. 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.”
He said that “We encourage you to adopt ODBC in any future version or new application development. You don’t need to change your existing applications using OLE DB, as they will continue to be supported for seven years from the launch of Denali, but you may want to consider migrating those applications to ODBC 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 our forum.”
“The marketplace is moving away from OLE DB and towards ODBC, with an eye towards supporting PHP and multi-platform solutions. Making this move to ODBC also drives more clarity for our C/C++ programmers who can now focus their efforts on one API,” Lam added.
In a releated news, the SQL Server team announced that “[…]We are working on our latest release of JDBC 4.0 which will come out with SQL Server codename “Denali.” We will fully support key features of SQL Server “Denali” such as “AlwaysOn,” along with core Java asks such as pure Java implementation of Kerberos integrated authentication.”
Here is a Quick Guide for OLE DB to ODBC Conversion: (read only)
You can download the OLE DB to ODBC Conversion guide here.