![]() ![]() Note that that both the 13.0 and 13.1 versions of this driver have the same “ODBC Driver 13 for SQL Server” display name listed under installed programs and ODBC Data Source Administrator. The current Microsoft ODBC Driver for SQL Server as of this writing is ODBC Driver 13 for SQL Server. The Data Access Technologies Road Map provides an overview and history of Microsoft data access technologies, which I recommend you peruse to ensure you are not inadvertently using deprecated or unsupported technologies for new development and, for existing applications, consider moving from legacy data access technologies to current ones when practical. The message is loud and clear that ODBC is the supported and preferred path for native applications going forward. This practice will facilitate more seamless upgrades to new versions of SQL Server and Azure SQL Database. Not only should SNAC not be used against SQL Server 2014 and later versions, the deprecated SQL Server OLE DB provider and ODBC driver that ship with Windows should also be avoided. This stand-alone ODBC driver is a free download from. unmanaged C++, VB6, VBA, Classic ASP, etc.) should generally use ODBC and the latest Microsoft ODBC Driver for SQL Server. The bottom line is that native Windows applications (e.g. Microsoft has a history of going out of their way to provide backwards compatibility in the SQL Server space but it’s been 3 SQL Server versions (soon to be 4 versions) since the deprecation announcement. The explicit block of OLE DB data access has yet not happened (as of this writing) but I think it’s prudent to heed the announcement and warning, at least for applications that currently use SQL Server 2014 and later versions as well as SQL Azure Database, or may need to use newer SQL versions in the future. ![]() It is recommended that you plan your migration soon to ODBC, if you want to start using newer versions of SQL Server as soon as they release. Question6: If I have an OLE DB application that I write for Denali, will it be supported on a post Denali version of SQL Server that is released during the life of Denali?Īnswer: No, in fact we may explicitly block the OLE DB applications on post-Denali versions of SQL Server. ![]() Below is an excerpt from the Microsoft is Aligning with ODBC for Native Relational Data Access FAQ which should be alarming to folks who continue to use Microsoft OLE DB providers to access SQL Server 2014 and later databases (note Denali is the code name for SQL Server 2012 and, again, emphasis mine): Even before SQL Server 2012 was released, Microsoft announced in August, 2011 that ODBC was the preferred technology for relational database access and that OLE DB was deprecated. Microsoft SQL Server 2012 Native Client is still installed and used as a component dependency to support these features in SQL Server 2014 and later versions, although that may change in the future. The warning does not apply to Microsoft SQL Server features and products that use SNAC as part of the OLE DB stack, like Linked Servers, SSIS, and SSAS. ![]() Let me first mention that the Books Online should have made it clear that this warning applies only to SNAC data access by applications. If you continue down the OLE DB path for data access in native code, use MSOLEDBSQL going forward. Keep in mind the legacy Microsoft OLE DB Provider for SQL Server (SQLOLEDB) remains deprecated. The initial release of MSOLEDBSQL does not support column level encryption with Always Encrypted so one must currently use SqlClient, ODBC, or JDBC when AE column encryption is required. This new driver will maintained out-of-band with the SQL Server database engine lifecycle, following the same release model as other SQL Server client drivers, facilitating incremental enhancements. Microsoft has decided to undeprecate (a new word) OLE DB and released a new OLE DB provider, Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL). The OLE DB story continues to evolve and I hope we see a roadmap and guidance from Microsoft soon. However, I still think it’s prudent to use the stand-alone ODBC driver instead of OLE DB for new native applications. The above warning was removed from the SQL Server documentation shortly after this article was first published. The Microsoft ODBC Driver for SQL Server provides native connectivity from Windows to Microsoft SQL Server and Microsoft Azure SQL Database. Avoid using SNAC in new development work, and plan to modify applications that currently use it. SQL Server Native Client (SNAC) is not supported beyond SQL Server 2012. I hope the warning excerpt below from the SQL Server Books Online is not a surprise to you (emphasis mine): ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |