. Qlik Community +4 Key Comparison for TLS 1.2 Implementation Feature Legacy Provider (SQLOLEDB) Modern Driver (MSOLEDBSQL) Status Deprecated Recommended OS Requirement Win10 / Server 2019+ for TLS 1.2 Any supported OS TLS 1.2 Support OS-dependent patch Native/Built-in New SQL Types Not supported Fully supported Connection String Provider=SQLOLEDB; Provider=MSOLEDBSQL; Best Practices & Common Issues 12 sites Does Microsoft OLE DB Provider for SQL Server support TLS 1.2 2 Sept 2017 —
Microsoft deprecated the old SQLOLEDB provider in favor of MSOLEDBSQL, which provides native support for TLS 1.2 and modern SQL Server features. microsoft ole db provider for sql server tls 1.2
Therefore, if your application uses Provider=SQLOLEDB and the SQL Server or Azure SQL Database requires TLS 1.2, the connection will fail with errors such as: Failure to do so results in connection failures,
(Use Integrated Security=SSPI if using classic NTLM/Kerberos instead of Azure AD) security audit findings
As part of industry-wide security initiatives (PCI DSS, NIST, HIPAA) and Microsoft’s deprecation of older TLS protocols (TLS 1.0 and 1.1), it is mandatory to ensure that all Microsoft OLE DB Provider for SQL Server connections use . Failure to do so results in connection failures, security audit findings, and exposure to protocol-level vulnerabilities (e.g., POODLE, BEAST). This document details the requirements, provider limitations, and step-by-step remediation for systems using the legacy SQLOLEDB provider and its modern replacement, MSOLEDBSQL .