TLS 1.2

  • OK, I have been doing a lot of research, and I am continuing that research, into some issues we are having with out SQL Servers since the implementation of TLS 1.2.  We are under the gun to get all of these issues resolved very quickly.  As I have been researching, I have found that all of our SQL Servers are at levels that are compatible with TLS 1.2  The issues we are dealing with are client connections and linked server configurations.  With all the time that has passed since TLS 1.2 came out and all the versions of client tools that have become available, I have a couple of questions that I hope you can help answer.

    For our ODBC connections, MS is currently up to version 18 of their driver (MSODBCSQL18.DLL).  Can you tell me if we are good to install this latest driver and have it compatible with SQL Server 2012 (SP4) (we are moving our last databases off right now but some will have to hang around a little longer), and up through SQL Server 2019, with TLS 1.2 enabled?  If not this version, what is the latest version we can use?

    For our linked servers, I have been looking at the providers and I see an MSOLEDBSQL on our newer versions of SQL server that I see we can use and it will work with TLS 1.2.  When I look at the ODBC providers, I see SQLNCL11, the SQL Server Native Client 11.0.  Is this the latest version of the native client and should I continue to use this one, or should I use the MSOLEDBSQL provider?

    Thanks for all help, in advance!



  • MSOLEDBSQL is the recommended provider. SQL Server Native Client is deprecated, apparently since 2014.

    Microsoft has been vacillating on data provider recommendations since at least the introduction of .NET.

    SQL Server OLEDB provider was deprecated in 2011, and undeprecated in 2018, and is the recommended provider for SQL Server. Note that SQLOLEDB is deprecated. "Microsoft OLE DB Driver for SQL Server" (MSOLEDBSQL) is the recommended provider.

    SQL Server Native Client remains deprecated, apparently since 2014.

    Microsoft briefly rekindled it's love for ODBC in 2011.


Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply