TLS 1.2 Support for SQL Server 2008, 2008 R2, 2012 and 2014
Published Jan 15 2019 04:50 PM 5,490 Views
First published on MSDN on Jan 31, 2016
Microsoft is pleased to announce the release of (Transport Layer Security) TLS 1.2 support in all major client drivers and SQL Server releases. The updates made available on January 29th, 2016 provide TLS 1.2 support for SQL Server 2008, SQL Server 2008 R2, SQL Server 2012 and SQL Server 2014 . The client drivers that have support for TLS 1.2 are SQL Server Native Client , Microsoft ODBC Driver for SQL Server , Microsoft JDBC Driver for SQL Server and ADO.NET (SqlClient) .

The list of SQL Server server and client component updates along with their download locations that support TLS 1.2 is available in the KB Article below:
3135244 TLS 1.2 support for Microsoft SQL Server

You can use KB3135244 to download the appropriate server and client component applicable for your environment. The first build numbers that provides complete TLS 1.2 support in each major release is available in KB3135244 as well. The following tables lists the client driver/components and server components which have TLS 1.2 support.
Client Components Server Components
SqlClient (.NET Framework 4.6) SQL Server 2014
SqlClient (.NET Framework 4.5.2, 4.5.1, 4.5) SQL Server 2012
SqlClient (.NET Framework 4.0) SQL Server 2008 R2
SqlClient (.NET Framework 3.5/a.k.a (.NET Framework 2.0 SP2) SQL Server 2008
MS ODBC Driver v11 (Windows)
SQL Server Native Client (for SQL Server 2012 & 2014)
SQL Server Native Client (for SQL Server 2008 R2)
SQL Server Native Client (for SQL Server 2008)
SQL Server Native Client (for SQL Server 2005)
JDBC 6.0
JDBC 4.2
JDBC 4.1

Known Issue: If you are on a currently using Cumulative Update for SQL Server 2014 and need to use TLS 1.2 for encrypted endpoints for features like Availability Groups, Database Mirroring or Service Broker, then we recommend that you wait till the next Cumulative Update for SQL Server 2014 (February 2016) which adds support for this particular scenario. This is documented as a known issue in KB3135852 . All the other branches mentioned in KB3135244 have support for this scenario.

Please feel free to post your questions and comments.
Version history
Last update:
‎Jan 15 2019 04:50 PM
Updated by: