![]() The use of "Microsoft OLEDB Driver for SQL Server" is what worked for us but I can also confirm Native Driver 11 also tests OK. This applies to Windows 10 and Windows Server 2019 or later. SQLOLEDB and the SQL Server ODBC driver (part of MDAC, shipped and serviced with Windows) has support for TLS 1.2 with Octobuild, version 17763.1554. Modern drivers like MSOLEDBSQL and ODBC Driver n for SQL Server are continuously improved to support latest SQL Server features and security standards. In summary, newer SQL Server client drivers provides more control over the specific driver and version without a direct OS patch level dependency. support for post-SQL 2000 data types) were added, though. Protocols when connecting to SQL Server using the data providers in ![]() End of support for the final 2012 SNAC version is July 12, 2012.įurthermore, as David called out in his answer, Microsoft recently added support for TLS 1.2 MDAC components in Windows 10 Build 17763.1554:Īdds support for the Transport Layer Security (TLS) 1.1 and 1.2 The SQL Server Native Client OLE DB driver is now deprecated in favor of MSOLEDBSQL. Change the connection string to Provider=MSOLEDBSQL after installation. See the Microsoft SQLNCLi team blog announcement. This new driver includes the support for the latest TLS 1.2 standards and is backwards compatible with SQL Server Native Client 11 (SQLNCLI11). The new OLE DB driver, MSOLEDBSQL, has been released. For example, I recall someone experiencing behavior differences with the SQL Server Native Client provider and ADO classic when server API cursors were used, although the commonly used firehose cursors were fine. Of course, once should test to avoid surprises. You should be able to install SQL Server Native Client 2012 and use that OLE DB provider with only a connection string change (change Provider=SQLOLEDB to Provider=SQLNCLI11). ![]() Your driver to one of the supported drivers listed in SQLOLEDB will not receive support for TLS 1.2. These have been deprecated since SQL 2005.Īccording to this blog post by the MSSQL Tiger Team: The SQLOLEDB provider and the SQL Server ODBC driver that ship with Windows are legacy components provided only for backwards compatibility.
0 Comments
Leave a Reply. |