Release notes - JDBC Driver for SQL Server

12.2 Compliance

Compliance change Details Fully compliant with JDBC API Specification 4.2. The jars in the 12.2 package are named according to Java version compatibility.

For example, the mssql-jdbc-12.2.0.jre11.jar file from the 12.2 package should be used with Java 11 (or higher). Compatible with Java Development Kit (JDK) version 19.0, 17.0, 11.0, and 1.8. Microsoft JDBC Driver 12.2 for SQL Server is now compatible with Java Development Kit (JDK) version 19.0 in addition to JDK 17.0, 11.0 and 1.8.

12.2 Releases

Download Microsoft JDBC Driver 12.2.0 for SQL Server (zip)
Download Microsoft JDBC Driver 12.2.0 for SQL Server (tar.gz)

Release number: 12.2.0
Released: January 31, 2023

New features in 12.2

Feature Details Java 19 support The driver is now compatible with Java Development Kit (JDK) version 19.0 in addition to JDK 17.0, 11.0 and 1.8. Added support for access token callback Allows client code to register a callback on a DataSource that returns an access token. Added support for DefaultAzureCredential Improvement to the user experience by supporting both


   DefaultAzureCredential

and


   IntelliJCredential

from the Azure Identity Library via the connection option


   authentication=ActiveDirectoryDefault

Changes in 12.2

Change Details Made driver Loom-friendly Replaces


   synchronized(foo)

with reentrant locks, improving performance when using Loom. Managed Identity authentication uses Azure Identity library Replaces the driver's built-in code to obtain and cache Managed Identity tokens with the Azure Identity library. This adds Managed Identity support for additional Azure services over what the driver previously supported. Updated dependencies Updated dependency versions for


   azure-identity


   azure-security-keyvault-keys


   antlr4-runtime


   bcprov-jdk15on


   bcpkix-jdk15on

, and


   msal

Fixes in 12.2

Details Fixed null SQL state and zero error code when database exception is thrown Fixed an issue where, after SQL Error, the SQL State and error code showed incorrect information. GitHub Issue #2015 . Fixed connecting to the wrong SQLServer host Fixes a concurrency issue where, when a driver is connecting to multiple SQLServer hosts, a connection could be established to the wrong host. GitHub Issue #1964 . Fixed cache account name casing issue Fixes an issue where account names were sent to the Microsoft Authentication Library with case-sensitivity, leading to repeated login requests. GitHub Issue #1923 . Fixed precision sent when using BigDecimal Fixes an issue where, by default, BigDecimal values were sent with maximum precision, which could result in undesired decimal rounding. GitHub Issue #1489 . GitHub Issue #942 Fixed attestation protocol


   NONE

to work in all cases Fixed logic behind


   NONE

attestation protocol to work in all cases, not just specific ones.

Previous releases

Download Microsoft JDBC Driver 11.2.3 for SQL Server (zip)
Download Microsoft JDBC Driver 11.2.3 for SQL Server (tar.gz)

Release number: 11.2.3
Released: January 12, 2023

11.2 Compliance

Compliance change Details Fully compliant with JDBC API Specification 4.2. The jars in the 11.2 package are named according to Java version compatibility.

For example, the mssql-jdbc-11.20.jre17.jar file from the 11.2 package should be used with Java 17. Compatible with Java Development Kit (JDK) version 18.0, 17.0, 11.0, and 1.8. Microsoft JDBC Driver 11.2 for SQL Server is now compatible with Java Development Kit (JDK) version 18.0 in addition to JDK 17.0, 11.0 and 1.8.

11.2 Releases

Release number: 11.2.3
Released: January 12, 2023

Fixed issues in 11.2.3:

Fixed null SQL state and zero error code when database exception is thrown

Fixed incorrect update counts when timeout occurs in batch queries

Fixed incorrect token expiration date when using Azure Functions

Fixed connecting to the wrong SQLServer host

Release number: 11.2.2
Released: December 15, 2022

Fixed issues in 11.2.2:

Fixed Idle Connection Resiliency bug

Clear prepared statement handle cache on idle reconnect

Fixed callable statement index out of bounds error

Fixed check for DONE token when fetching result sets

Fixed intermittent error: "Internal error during decryption: Tag mismatch!"

Download Microsoft JDBC Driver 11.2.2 for SQL Server (zip)
Download Microsoft JDBC Driver 11.2.2 for SQL Server (tar.gz)

Release number: 11.2.1
Released: September 8, 2022

Fixed issues in 11.2.1:

Made


    com.microsoft.azure:msal4j

an optional dependency

Fixed a query cancellation bug that intermittently occurred in batch queries

Download Microsoft JDBC Driver 11.2.1 for SQL Server (zip)
Download Microsoft JDBC Driver 11.2.1 for SQL Server (tar.gz)

Release number: 11.2.0
Released: August 4, 2022

Download Microsoft JDBC Driver 11.2.0 for SQL Server (zip)
Download Microsoft JDBC Driver 11.2.0 for SQL Server (tar.gz)

New features in 11.2

Feature Details Java 18 support The driver is now compatible with Java Development Kit (JDK) version 18.0 in addition to JDK 17.0, 11.0 and 1.8. Added Configurable IPv6 Support The IP address preference for the client application can now be set between IPv4 and IPv6. Use the new


   ipaddresspreference

connection setting to control the behavior. For more information, see Setting the connection properties . Added support for prepare method selection Added new connection string property prepareMethod to toggle between use of sp_prepare and sp_prepexec. Use the new


   prepareMethod

connection setting to control the behavior. For more information, see Setting the connection properties . Cache parameter metadata calls Encryption-related information for parameterized queries can now be cached. See Using Always Encrypted with the JDBC driver .

Changes in 11.2

Change Details TDS 8.0 support by adding "strict" option to encrypt connection property BREAKING CHANGE Encrypt connection property is now of type string. Added check for negotiated ALPN Checks to make sure to Application-Layer Protocol is successfully negotiated. Added an option for enclaveAttestationProtocol Added option for


   NONE

protocol so that secure enclaves can be used without attestation. Allow serverName to be re-ordered in connection string Validate that the serverName field of the connection string does not have an equal sign.


   msal4j

dependency is now explicit Added an explicit dependency for


   msal4j

(was a transitive dependency in previous releases). Updated dependencies Updated dependency versions for


   azure-identity


   azure-security-keyvault-keys

Fixes in 11.2

Details Managed Identity Retry interval Fixed Managed Identity retry interval to properly back off exponentially GitHub Issue #1765 . Exception is not thrown as expected when the session is killed in SQL database Added check for DONE_ERROR status token which may occur from a killed session on the server GitHub Issue #1846 . Assertion fails when canceling "insert into" statement Fixed issue where the driver may assert when canceling a statement GitHub Issue #1849 . Establishing multiple connections in parallel can throw an IndexOutOfBoundsException Fixed race condition with addressList which may result in IndexOutOfBoundsException when establishing multiple connections GitHub Issue #1852 . Download Microsoft JDBC Driver 10.2.3 for SQL Server (zip)
Download Microsoft JDBC Driver 10.2.3 for SQL Server (tar.gz)

Release number: 10.2.3 Released: Jan 12, 2023

Release number: 10.2.2 Released: Dec 13, 2022

Download Microsoft JDBC Driver 10.2.2 for SQL Server (zip)
Download Microsoft JDBC Driver 10.2.2 for SQL Server (tar.gz)

Release number: 10.2.1
Released: May 12, 2022

Download Microsoft JDBC Driver 10.2.1 for SQL Server (zip)
Download Microsoft JDBC Driver 10.2.1 for SQL Server (tar.gz)

10.2 Compliance

Compliance change Details Fully compliant with JDBC API Specification 4.2. The jars in the 10.2 package are named according to Java version compatibility.

For example, the mssql-jdbc-10.20.jre17.jar file from the 10.2 package should be used with Java 17. Compatible with Java Development Kit (JDK) version 17.0, 11.0, and 1.8. Microsoft JDBC Driver 10.2 for SQL Server is now compatible with Java Development Kit (JDK) version 17.0 in addition to JDK 11.0 and 1.8.

10.2 Releases

Release number: 10.2.3 Released: Jan 12, 2023

Fixed issues in 10.2.3:

Fixed incorrect update counts when timeout occurs in batch queries

Fixed incorrect token expiration date when using Azure Functions

Fixed null SQL state and zero error code when database exception is thrown

Release number: 10.2.2
Released: Dec 13, 2022

Fixed issues in 10.2.2:

Clear prepared statement cache on idle connection resiliency reconnections

Fix for setting KeepAlive extended options

Fixed issue where the driver may assert when canceling a statement

Fixed callable statement index out of bounds error

Fixed issue not checking for DONE token errors so exceptions are ignored

Fixed query cancellation bug

Release number: 10.2.1
Released: May 12, 2022

Fixed issues in 10.2.1:

Changed Idle Connection Resiliency timeout to use existing SharedTimer

Fixed Managed Identity authentication retry interval to exponentially back off properly

Removed extraneous call to executeCommand() within connectionCommand()

Release number: 10.2.0
Released: January 31, 2022

Download Microsoft JDBC Driver 10.2.0 for SQL Server (zip)
Download Microsoft JDBC Driver 10.2.0 for SQL Server (tar.gz)

New features in 10.2

Feature Details Java 17 support The driver is now compatible with Java Development Kit (JDK) version 17.0 in addition to JDK 11.0 and 1.8. Idle Connection Resiliency support Idle Connection Resiliency is now supported. See Idle Connection Resiliency . Multi-user Key Store Providers The driver now supports Key Store providers at the connection and statement level to support multi-user scenarios. See Using Always Encrypted with the JDBC driver .

Changes in 10.2

Change Details Certificate validation when encrypt = false BREAKING CHANGE When encrypt = false but the server requires encryption, the certificate will be validated based on the trustServerCertificate connection setting. aadSecurePrincipalId and aadSecurePrincipalSecret deprecated The aadSecurePrincipalId and aadSecurePrincipalSecret connection properties have been deprecated. Use username and password instead. getAADSecretPrincipalId API removed BREAKING CHANGE The getAADSecretPrincipalId API has been removed for security reasons. SQL_Variant support Added support for SQL_Variant datatype when retrieving DateTimeOffset. Non-blocking random in Linux Updated to use a non-blocking random call when generating a GUID for enclave packages. CNAME resolution for realm Added CNAME resolution when realm is specified. Updated dependencies Updated dependency versions for


   azure-identity


   azure-security-keyvault-keys


   gson

, and


   bouncycastle

Fixes in 10.2

Details Download Microsoft JDBC Driver 9.4.1 for SQL Server (zip)
Download Microsoft JDBC Driver 9.4.1 for SQL Server (tar.gz)

Release number: 9.4.1
Released: December 7, 2021

9.4 Compliance

Compliance change Details Fully compliant with JDBC API Specification 4.2. The jars in the 9.4 package are named according to Java version compatibility.

For example, the mssql-jdbc-9.4.0.jre16.jar file from the 9.4 package should be used with Java 16. Compatible with Java Development Kit (JDK) version 16.0, 11.0, and 1.8. Microsoft JDBC Driver 9.4 for SQL Server is now compatible with Java Development Kit (JDK) version 16.0 in addition to JDK 11.0 and 1.8.

9.4 Releases

Version number: 9.4.1
Released: December 07, 2021

Fixed issues in 9.4.1:

Fixed potential hang when the driver encounters unsupported TDS_COLMETADATA

Fixed conversion of LocalDateTime and LocalTime to String in Bulk Copy

Version number: 9.4.0
Released: July 30, 2021

Download Microsoft JDBC Driver 9.4.0 for SQL Server (zip)
Download Microsoft JDBC Driver 9.4.0 for SQL Server (tar.gz)

New features in 9.4

Feature Details Java 16 support The driver is now compatible with Java Development Kit (JDK) version 16.0 in addition to JDK 11.0 and 1.8. Replication connection support Replication connections are now supported. See Setting the connection properties . Custom Kerberos authentication realm The driver now supports specifying a custom authentication realm when using Kerberos authentication. See Setting the connection properties . Open Connection Retry The


   connectRetryCount

and


   connectRetryInterval

connection properties have been added to configure automatic retries when opening connections. See Setting the connection properties for details on these new properties.

Changes in 9.4

Change Details Azure Key Vault Provider Multiple, successive connections can be opened that specify different Azure Key Vault provider information. Updated error messages Error messages related to Enclave exceptions now include a link to a troubleshooting guide.
Error messages related to Active Directory authentication failures now include the error string from the underlying library. Driver version sent to server The driver version is now correctly sent to the database during


   PRELOGIN

. Client process ID The client process ID is now sent to the server when running on Java 9+. Java 8 keeps the previous functionality of sending

for the client process ID. Updated dependencies Updated dependency versions for


   azure-identity


   azure-security-keyvault-keys


   gson


   antlr

, and


   bouncycastle

. Removed unnecessary references Removed unused Java 9-specific class references from the Java 8 jar

Fixes in 9.4

Details GitHub Issue #1499 Fixed: Batch fails when always encrypted is enabled in the connection string and clearParameters is called. GitHub Issue #1632 Fixed: Small memory leak on new connection. GitHub Issue #1565 Fixed an issue where trustStorePassword is null when using applicationIntent=ReadOnly GitHub Issue #1568 Fixed an issue where redirected token contains named instance in servername GitHub Issue #1531 Fixed potential integer overflow in TDSWriter.writeString() Download Microsoft JDBC Driver 9.2.1 for SQL Server (zip)
Download Microsoft JDBC Driver 9.2.1 for SQL Server (tar.gz)

Version number: 9.2.1
Released: March 02, 2021

9.2 Compliance

Compliance change Details Fully compliant with JDBC API Specification 4.2. The jars in the 9.2 package are named according to Java version compatibility.

For example, the mssql-jdbc-9.2.1.jre15.jar file from the 9.2 package should be used with Java 15. Compatible with Java Development Kit (JDK) version 15.0, 11.0, and 1.8. Microsoft JDBC Driver 9.2 for SQL Server is now compatible with Java Development Kit (JDK) version 15.0 in addition to JDK 11.0 and 1.8.

9.2 Releases

Version number: 9.2.1
Released: March 02, 2021

Fixed issues in 9.2.1:

Fixed an issue with client secret being empty during ActiveDirectoryServicePrincipal authentication in Azure environment.

Version number: 9.2.0
Released: January 29, 2021

Download Microsoft JDBC Driver 9.2.0 for SQL Server (zip)
Download Microsoft JDBC Driver 9.2.0 for SQL Server (tar.gz)

Support for JDK 15

Microsoft JDBC Driver 9.2 for SQL Server is now compatible with Java Development Kit (JDK) version 15.0 in addition to JDK 11.0 and 1.8.

Added support for Azure Active Directory Interactive Authentication

Authentication type addition Details Microsoft JDBC Driver 9.2 for SQL Server now supports authentication to Azure Key Vault via interactive authentication. See Connecting using Azure Active Directory authentication .

Added support for Azure Active Directory Service Principal Authentication

Authentication type addition Details Microsoft JDBC Driver 9.2 for SQL Server now supports authentication to Azure Key Vault using the client ID and secret of a service principal identity. See Connecting using Azure Active Directory authentication .

Updated Azure Key Vault library to use modern Azure Key Vault library

Library changes for Azure Key Vault Details Microsoft JDBC Driver 9.2 migrated from the previous-generation Azure Key Vault library and ADAL libraries to the more modern Azure Key Vault and Azure Identity equivalents. DEPENDENCY CHANGE Make sure you update your application dependencies if you take advantage of Azure Active Directory authentication or Azure Key Vault. See the dependency requirements when work with the Azure Key Vault provider or Azure Active Directory authentication

Enabled useBulkCopyForBatchInsert for non-Azure Synapse Analytics servers

useBulkCopyForBatchInsert changes for non Azure Synapse Analytics servers Details Microsoft JDBC Driver 9.2 now allows bulk copy API for batch insert operation against non-Azure Synapse Analytics servers. See Using bulk copy API for batch insert operation . Download Microsoft JDBC Driver 8.4 for SQL Server (zip)
Download Microsoft JDBC Driver 8.4 for SQL Server (tar.gz)

Version number: 8.4.1
Released: August 27, 2020

8.4 Compliance

Compliance change Details Fully compliant with JDBC API Specification 4.2. The jars in the 8.4 package are named according to Java version compatibility.

For example, the mssql-jdbc-8.4.1.jre14.jar file from the 8.4 package should be used with Java 14. Compatible with Java Development Kit (JDK) version 14.0, 11.0, and 1.8. Microsoft JDBC Driver 8.4 for SQL Server is now compatible with Java Development Kit (JDK) version 14.0 in addition to JDK 11.0 and 1.8.

8.4 Releases

Version number: 8.4.1
Released: August 27, 2020
Fixed issues:

Fixed an issue with


    SQLServerConnectionPoolProxy

not being compatible with


    delayLoadingLobs

Fixed a potential


    NullPointerException

issue with


    delayLoadingLobs

Fixed an issue with decrypting column encryption keys when using the Windows Certificate Store

Version number: 8.4.0
Released: July 31, 2020

Support for JDK 14

Microsoft JDBC Driver 8.4 for SQL Server is now compatible with Java Development Kit (JDK) version 14.0 in addition to JDK 11.0 and 1.8.

Added support for authentication to Azure Key Vault using Managed Identity

Authentication type addition Details Microsoft JDBC Driver 8.4 for SQL Server now supports authentication to Azure Key Vault using Managed Identity. See Using Always Encrypted with the JDBC driver .

Extended support for bulk copy for Azure Data Warehouse

Bulk copy changes for Azure Data Warehouse Details Microsoft JDBC Driver 8.4 adds a new connection property,


   sendTemporalDataTypesAsStringForBulkCopy

. This boolean property is TRUE by default. See Using bulk copy with the JDBC driver .

Added support for Azure SQL DNS caching

DNS Caching Details Microsoft JDBC Driver 8.4 for SQL Server added a new connection property


   delayLoadingLobs

. Setting


   delayLoadingLobs

to FALSE will cause all LOB objects retrieved from the ResultSet to not be streamed. This means that the driver will load the entire LOB object into memory at once, similar to how the driver was functioning before version 6.4 release.

Added support for client certificate authentication for loopback scenarios

Client certificate authentication Details Microsoft JDBC Driver 8.4 for SQL Server added a new authentication method called client certificate authentication for loopback scenarios. See Client Certificate Authentication for Loopback Scenarios . Download Microsoft JDBC Driver 8.2 for SQL Server (zip)
Download Microsoft JDBC Driver 8.2 for SQL Server (tar.gz)

Version number: 8.2.2 Released: March 24, 2020

8.2 Compliance

Compliance change Details Fully compliant with JDBC API Specification 4.2. The jars in the 8.2 package are named according to Java version compatibility.

For example, the mssql-jdbc-8.2.2.jre11.jar file from the 8.2 package should be used with Java 11. Compatible with Java Development Kit (JDK) version 13.0, 11.0, and 1.8. Microsoft JDBC Driver 8.2 for SQL Server is now compatible with Java Development Kit (JDK) version 13.0 in addition to JDK 11.0 and 1.8.

8.2 Releases

Version number: 8.2.2
Released: March 24, 2020
Fixed issues:

Added an option to configure the list of trusted Azure Key Vault endpoints

Version number: 8.2.1
Released: February 26, 2020
Fixed issues:

Fixed a potential


    NullPointerException

issue when retrieving data as


    java.time.LocalTime


    java.time.LocalDate

type with


    SQLServerResultSet.getObject()

Version number: 8.2.0
Released: January 31, 2020

Support for JDK 13

Microsoft JDBC Driver 8.2 for SQL Server is now compatible with Java Development Kit (JDK) version 13.0 in addition to JDK 11.0 and 1.8.

Always Encrypted with secure enclaves

Always Encrypted change Details Microsoft JDBC Driver 8.2 for SQL Server has improved performance when retrieving temporal datatypes from SQL Server. This change eliminates unnecessary temporal datatype conversions by eliminating the use of java.util.Calendar wherever possible. The following is a list of the temporal datatypes that have been affected by this performance improvement; in format SQL Server datatype followed by the respective Java mapping. date (java.sql.Date), datetime (java.sql.Timestamp), datetime2 (java.sql.Timestamp), smalldatetime (java.sql.Timestamp), and time (java.sql.Time).

¹ Due to the differences in how time zones are handled between java.util.Calendar and java.time.LocalDateTime API, temporal datatypes with a user provided java.util.Calendar object associated with it or microsoft.sql.DateTimeOffset datatypes do not benefit from this improvement.

Deployment of mssql-jdbc_auth-<version>-<arch>.dll (previously sqljdbc_auth.dll) to Maven Repository

sqljdbc_auth.dll change Details Download Microsoft JDBC Driver 7.4.1 for SQL Server (self-extracting exe)
Download Microsoft JDBC Driver 7.4.1 for SQL Server (tar.gz)

Version number: 7.4.1
Released: August 2, 2019

7.4 Compliance

Compliance change Details Fully compliant with JDBC API Specification 4.2. The jars in the 7.4 package are named according to Java version compatibility.

For example, the mssql-jdbc-7.4.1.jre11.jar file from the 7.4 package should be used with Java 11. Compatible with Java Development Kit (JDK) version 12.0, 11.0, and 1.8. Microsoft JDBC Driver 7.4 for SQL Server is now compatible with Java Development Kit (JDK) version 12.0 in addition to JDK 11.0 and 1.8.

7.4 Releases

Version number: 7.4.1
Released: August 2, 2019
Fixed issues:

Reverted new


    hashCode()

and


    equals()

API implementations from


    SQLServerDataTable

and


    SQLServerDataColumn

as the API change broke backwards compatibility

Version number: 7.4.0
Released: July 31, 2019

Support for JDK 12

Microsoft JDBC Driver 7.4 for SQL Server is now compatible with Java Development Kit (JDK) version 12.0 in addition to JDK 11.0 and 1.8.

Introduces NTLM authentication

NTLM change Details Supports NTLM authentication mode. This mode of authentication allows both Windows and non-Windows clients to authenticate themselves against SQL Server using Windows domain users. More details and a sample application to use this authentication mode. See Connecting using NTLM Authentication .

Introduces querying ParameterMetaData via useFmtOnly

useFmtOnly change Details useFmtOnly connection property added. This feature allows users to optionally query ParameterMetaData via the


   SET FMTONLY ON

legacy API. This is useful for scenarios where


   sp_describe_undeclared_parameters

doesn't perform as expected. More details and limitations. See Using useFmtOnly

Updated Microsoft Azure Key Vault SDK for Java , version 1.2.1

Key Vault SDK change Details When using NTLM Authentication. Enabling Extended Protection and encrypted connections at the same time is currently not supported. When using useFmtOnly. There are some issues with the feature, which are caused by deficiencies in SQL parsing logic. See Using useFmtOnly for more details and workaround suggestions.

7.2.2

Download Microsoft JDBC Driver 7.2.2 for SQL Server (self-extracting exe)
Download Microsoft JDBC Driver 7.2.2 for SQL Server (tar.gz)

Version number: 7.2.2
Released: April 16, 2019

7.2 Compliance

Compliance change Details Fully compliant with JDBC API Specification 4.2. The jars in the 7.2 package are named according to Java version compatibility.

For example, the mssql-jdbc-7.2.2.jre11.jar file from the 7.2 package should be used with Java 11. Compatible with Java Development Kit (JDK) version 11.0 in addition to JDK 1.8. Microsoft JDBC Driver 7.2 for SQL Server is now compatible with Java Development Kit (JDK) version 11.0 in addition to JDK 1.8.

7.2 Releases

Version number: 7.2.2
Released: April 16, 2019
Fixed issues:

Fixed issues with ActivityIDs not getting cleaned up properly

Version number: 7.2.1
Released: February 11, 2019
Fixed issues:

Fixed parsing issues with certain parameterized queries

Version number: 7.2.0
Released: January 31, 2019

Active Directory Managed Identity (MSI) authentication

MSI change Details Supports Active Directory Managed Identity (MSI) authentication mode. This mode of authentication is applicable on Azure Resources with support for the "Identity" feature enabled.

Both types of Managed Identities (MSI) are supported by the driver to acquire accessToken for establishing secure connection. More details and a sample application to use this authentication mode. See Connecting using Azure Active Directory Authentication .

Introduces Open Service Gateway Initiative (OSGi) support

OSGi change Details DataSourceFactory implementation added. •


   org.osgi.service.jdbc.DataSourceFactory

•


   com.microsoft.sqlserver.jdbc.osgi.SQLServerDataSourceFactory

Activator implementation added. •


   org.osgi.framework.BundleActivator

•


   com.microsoft.sqlserver.jdbc.osgi.Activator

Introduces SQLServerError APIs

Error API change Details SQLServerError API introduced. Getter APIs to retrieve additional details about the error generated from the server.

•


   SQLServerException.getSQLServerError()

•


   SQLServerError

Additional details. See Handling Errors .

Updated Microsoft Azure Active Directory Authentication Library (ADAL4J) for Java , version 1.6.3

ADAL4J change Details Parameterized queries, in certain cases. An update of the 7.2.0 version, v7.2.1, was released in February 2019 to address this issue. Cleaning up of ActivityIds. An update of the 7.2.1 version, v7.2.2, was released in April 2019 to address this issue. Download Microsoft JDBC Driver 7.0 for SQL Server (self-extracting exe)
Download Microsoft JDBC Driver 7.0 for SQL Server (tar.gz)

Version number: 7.0.0
Released: July 31, 2018

Microsoft JDBC Driver 7.0 for SQL Server is fully compliant with JDBC API Specification 4.2. The jars in the 7.0 package are named according to Java version compatibility. For example, the mssql-jdbc-7.0.0.jre10.jar file from the 7.0 package should be used with Java 10.

Support for JDK 10

Microsoft JDBC Driver 7.0 for SQL Server is now compatible with Java Development Kit (JDK) version 10.0 in addition to JDK 1.8. This update also exposes the driver's Automatic-Module-Name as com.microsoft.sqlserver.jdbc through its MANIFEST file.

Support for spatial datatypes

Microsoft JDBC Driver 7.0 for SQL Server now provides support for SQL Server spatial datatypes Geography and Geometry. For more information about spatial datatype APIs and how to use them, see Using spatial datatypes .

Implementation for JDBC 4.3 introduced java.sql.Connection APIs beginRequest() and endRequest()

Microsoft JDBC Driver 7.0 for SQL Server now implements beginRequest() and endRequest() APIs from the java.sql.Connection class. These APIs were introduced with JDBC 4.3 specifications and JDK 9. For more information about the driver's implementation of these APIs, see JDBC 4.3 compliance for the JDBC Driver .

Support for SQL Data Discovery and Classification

Microsoft JDBC Driver 7.0 for SQL Server provides support for SQL Data Discovery and Classification with any target database that supports this feature. The driver now exposes SQLServerResultSet.getSensitivityClassification() APIs to extract this information from the fetched ResultSet .

For more information about how to use this feature with the JDBC Driver, see the sample in SQL Data Discovery and Classification .

Added connection property: useBulkCopyForBatchInsert

Microsoft JDBC Driver 7.0 for SQL Server introduces a new connection property, useBulkCopyForBatchInsert . This property is supported only for Azure Synapse Analytics.

This property is disabled by default. You can enable it to increase performance of user applications when you're pushing large amounts data to Azure Synapse Analytics. Enabling this property changes the behavior of batch insert operations to switch to bulk copy operations with user-provided data. For more information about this property and its limitations, see Using Bulk Copy API for batch insert operation .

Added connection property: cancelQueryTimeout

Microsoft JDBC Driver 7.0 for SQL Server introduces a new connection property, cancelQueryTimeout , to cancel queryTimeout on java.sql.Connection and java.sql.Statement objects.

Added Azure Key Vault Provider constructors

Microsoft JDBC Driver 7.0 for SQL Server reintroduces a previously removed constructor, for SQLServerColumnEncryptionAzureKeyVaultProvider . It allowed authentication through a custom method implemented over SQLServerKeyVaultAuthenticationCallback to fetch an access token.

The new constructors have the following definition:

/* This constructor is added to provide backward compatibility with 6.0
* version of the driver. It is marked deprecated for removal in the next
* stable release.
@Deprecated
public SQLServerColumnEncryptionAzureKeyVaultProvider(
        SQLServerKeyVaultAuthenticationCallback authenticationCallback,
        ExecutorService executorService) throws SQLServerException;
/*New constructor to replace the above constructor*/
public SQLServerColumnEncryptionAzureKeyVaultProvider(
            SQLServerKeyVaultAuthenticationCallback authenticationCallback) throws SQLServerException;
Updated "Microsoft Azure Active Directory Authentication Library (ADAL4J) for Java" version: 1.6.0
Microsoft JDBC Driver 7.0 for SQL Server has updated its Maven dependency on "Microsoft Azure Active Directory Authentication Library (ADAL4J) for Java" to version 1.6.0. For more information about dependencies, see Feature dependencies of the Microsoft JDBC Driver for SQL Server.
 Download Microsoft JDBC Driver 6.4 for SQL Server (self-extracting exe)

 Download Microsoft JDBC Driver 6.4 for SQL Server (tar.gz)
Version number: 6.4.0

Released: February 27, 2018
If you need to download the driver in a language other than the one detected for you, you can use these direct links.

For the driver in a self-extracting exe file: Chinese (Simplified) | Chinese (Traditional) | English (United States) | French | German | Italian | Japanese | Korean | Portuguese (Brazil) | Russian | Spanish

For the driver in a tar.gz file: Chinese (Simplified) | Chinese (Traditional) | English (United States) | French | German | Italian | Japanese | Korean | Portuguese (Brazil) | Russian | Spanish
Microsoft JDBC Driver 6.4 for SQL Server is fully compliant with JDBC specifications 4.1 and 4.2. The jars in the 6.4 package are named according to Java version compatibility. For example, the mssql-jdbc-6.4.0.jre8.jar file from the 6.4 package must be used with Java 8.
Support for JDK 9
The driver supports JDK version 9.0 in addition to JDK 8.0 and 7.0.
JDBC 4.3 compliance
The driver supports the Java Database Connectivity API 4.3 specification, in addition to 4.1 and 4.2. The JDBC 4.3 API methods are added but not implemented yet. For details, see JDBC 4.3 compliance for the JDBC Driver.
Added connection property: sslProtocol
A new connection property lets users specify the TLS protocol keyword. Possible values are: "TLS", "TLSv1", "TLSv1.1", and "TLSv1.2". For details, see SSLProtocol.
Deprecated connection property: fipsProvider
The connection property fipsProvider is removed from the list of accepted connection properties. For details, see the related GitHub pull request.
Added connection properties for specifying a custom TrustManager
The driver now supports specifying a custom TrustManager with added trustManagerClass and trustManagerConstructorArg connection properties. You can dynamically specify a set of certificates that are trusted on a per-connection basis without modifying the global settings for the Java virtual machine (JVM) environment.
Added support for datetime/smallDatetime in table-valued parameters
The driver now supports the datatypes datetime and smallDatetime when you're using table-valued parameters (TVPs).
Added support for the sql_variant datatype
The JDBC Driver now supports sql_variant datatypes to be used with SQL Server. The sql_variant datatype is also supported with features such as TVPs and bulk copy with the following limitations:




    

For date values:
When you're using a TVP to populate a table that contains datetime, smalldatetime, or date values stored in a sql_variant column, calling the getDateTime(), getSmallDateTime(), or getDate() method on the result set doesn't work and throws the following exception:
java java.lang.String cannot be cast to java.sql.Timestamp
As a workaround, use the getString() or getObject() method instead.
Using a TVP with sql_variant for null values:
If you're using a TVP to populate a table and send a NULL value to the sql_variant column type, you'll encounter an exception. Inserting a NULL value with the column type sql_variant in a TVP is currently not supported.
Implemented prepared statement metadata caching
The JDBC Driver has implemented prepared statement metadata caching for performance improvement. The driver now supports caching prepared statement metadata in the driver with disableStatementPooling and statementPoolingCacheSize connection properties. This feature is disabled by default. For more information, see Prepared statement metadata caching for the JDBC Driver.
Added support for Azure AD Integrated Authentication on Linux/macOS
The JDBC Driver now supports Azure Active Directory (Azure AD) Integrated Authentication on all supported operating systems (Windows, Linux, and macOS) with Kerberos. Alternatively, on Windows operating systems, users can authenticate with mssql-jdbc_auth-<version>-<arch>.dll.
Updated "Microsoft Azure Active Directory Authentication Library (ADAL4J) for Java" version: 1.4.0
The JDBC Driver has updated its Maven dependency on "Microsoft Azure Active Directory Authentication Library (ADAL4J) for Java" to version 1.4.0. For more information about dependencies, see Feature dependencies of the Microsoft JDBC Driver for SQL Server.
 Download Microsoft JDBC Driver 6.2 for SQL Server (self-extracting exe)

 Download Microsoft JDBC Driver 6.2 for SQL Server (tar.gz)
Version number: 6.2.2

Released: September 29, 2017
If you need to download the driver in a language other than the one detected for you, you can use these direct links.

For the driver in a self-extracting exe file: Chinese (Simplified) | Chinese (Traditional) | English (United States) | French | German | Italian | Japanese | Korean | Portuguese (Brazil) | Russian | Spanish

For the driver in a tar.gz file: Chinese (Simplified) | Chinese (Traditional) | English (United States) | French | German | Italian | Japanese | Korean | Portuguese (Brazil) | Russian | Spanish
Microsoft JDBC Driver 6.2 for SQL Server is fully compliant with JDBC specifications 4.1 and 4.2. The jars in the 6.2 package are named according to Java version compatibility. For example, the mssql-jdbc-6.2.2.jre8.jar file from the 6.2 package is recommended for use with Java 8.
6.2 Releases
Version number: 6.2.2

Released: October 3, 2017

Fixed issues:
Updated ADAL4J dependency to version 1.2.0 and Azure Key Vault dependency to version 1.0.0
Version number: 6.2.1

Released: July 14, 2017

Fixed issues:
Fixed an issue when running queries without parameters using preparedStatement
Version number: 6.2.0

Released: June 30, 2017
An issue with the metadata caching improvement was found in the JDBC 6.2 RTW released on June 29, 2017. The improvement was rolled back and new jars (version 6.2.1) were released on July 17, 2017.
Another improvement upgraded the Azure Key Vault dependent library version to 1.0.0, and new jars (version 6.2.2) were released on October 19, 2017.
Download the latest updates for JDBC Driver 6.2 via the above links, GitHub, or Maven Central. Please update your projects to use the 6.2.2 release jars. For more information, view release notes for 6.2.1 and 6.2.2.
Azure AD support for Linux
Connect your Linux applications to Azure SQL Database by using Azure AD authentication via username/password and access token methods.
FIPS-enabled JVMs
The JDBC Driver can now be used on JVMs that run in Federal Information Processing Standard (FIPS) 140 compliance mode to meet federal standards on compliance.
Kerberos authentication improvements
The JDBC Driver now has support for:
Principal/password method for applications where the Kerberos configuration can't be modified or can't retrieve a new token or keytab. This method can be used for authenticating to a SQL Server instance that allows only Kerberos authentication.
Cross-realm authentication that uses Kerberos Integrated Authentication without explicitly setting the server SPN. The driver now automatically computes the realm even when it isn't provided.
Kerberos Constrained Delegation by accepting impersonated user credentials as a GSS credential object via data source. This impersonated credential is then used to establish a Kerberos connection.
Added timeouts
The JDBC Driver now supports the following configurable timeouts. You can change them based on your application's needs.
Query timeout to control the number of seconds to wait before a timeout occurs when you're running a query.
Socket timeout to specify the number of milliseconds to wait before a timeout occurs on a socket read or accept.
Version number: 6.1.0

Released: November 17, 2016
Microsoft JDBC Driver 6.1 for SQL Server is fully compliant with JDBC specifications 4.1 and 4.2. This is the initial open-source release of the JDBC Driver. The source code can be found at the GitHub v6.1.0 tag. It builds the mssql-jdbc-6.1.0.jre8.jar and mssql-jdbc-6.1.0.jre7.jar files, which correspond to Java version compatibility.
 Download Microsoft JDBC Driver 6.0 for SQL Server (self-extracting exe)

 Download Microsoft JDBC Driver 6.0 for SQL Server (tar.gz)
Version number: 6.0.8112

Released: January 17, 2017
If you need to download the driver in a language other than the one detected for you, you can use these direct links.

For the driver in a self-extracting exe file: Chinese (Simplified) | Chinese (Traditional) | English (United States) | French | German | Italian | Japanese | Korean | Portuguese (Brazil) | Russian | Spanish

For the driver in a tar.gz file: Chinese (Simplified) | Chinese (Traditional) | English (United States) | French | German | Italian | Japanese | Korean | Portuguese (Brazil) | Russian | Spanish
Microsoft JDBC Driver 6.0 for SQL Server is fully compliant with JDBC specifications 4.1 and 4.2. The jars in the 6.0 package are named according to their compliance with the JDBC API version. For example, the sqljdbc42.jar file from the 6.0 package is JDBC API 4.2 compliant. Similarly, the sqljdbc41.jar file is compliant with JDBC API 4.1.
To ensure that you have the right sqljdbc42.jar or sqljdbc41.jar file, run the following lines of code. If the output is "Driver version: 6.0.7507.100", you have the JDBC Driver 6.0 package.
Connection conn = DriverManager.getConnection("jdbc:sqlserver://<server>;encrypt=true;user=<user>;password=<password>;");
System.out.println("Driver version: " + conn.getMetaData().getDriverVersion());
Always Encrypted
The driver supports the Always Encrypted feature in SQL Server 2016. This feature ensures that sensitive data is never seen in plaintext in a SQL Server instance. Always Encrypted works by transparently encrypting the data in the application, so that SQL Server will handle only the encrypted data and not plaintext values. Even if the SQL Server instance or the host machine is compromised, all an attacker can get is ciphertext of sensitive data. For details, see Using Always Encrypted with the JDBC Driver.
Internationalized domain names
The driver supports internationalized domain names (IDNs) for server names. For details, see "Using International Domain Names" in the International features of the JDBC Driver article.
Parameterized queries
The driver now supports retrieving parameter metadata with prepared statements for complex queries, such as subqueries and/or joins. Note that this improvement is available only when you're using SQL Server 2012 and newer versions.
Azure Active Directory
Azure AD authentication is a mechanism of connecting to Azure SQL Database using identities in Azure AD. Use Azure AD authentication to centrally manage identities of database users and as an alternative to SQL Server authentication.
You can use JDBC Driver 6.0 to specify your Azure AD credentials in the JDBC connection string to connect to Azure SQL Database. For details, see the authentication property in the Setting the connection properties article.
Table-valued parameters
TVPs provide an easy way to marshal multiple rows of data from a client application to SQL Server without requiring multiple round trips or special server-side logic for processing the data. You can use TVPs to encapsulate rows of data in a client application and send the data to the server in a single parameterized command. The incoming data rows are stored in a table variable that you can then operate on by using Transact-SQL. For details, see Using table-valued parameters.
Always On Availability Groups
The driver now supports transparent connections to Always On Availability Groups. The driver quickly discovers the current Always On topology of your server infrastructure and connects to the current active server transparently.
 Download Microsoft JDBC Driver 4.2 for SQL Server (self-extracting exe)

 Download Microsoft JDBC Driver 4.2 for SQL Server (tar.gz)
Version number: 4.2.8112

Released: August 24, 2015
If you need to download the driver in a language other than the one detected for you, you can use these direct links.

For the driver in a self-extracting exe file: Chinese (Simplified) | Chinese (Traditional) | English (United States) | French | German | Italian | Japanese | Korean | Portuguese (Brazil) | Russian | Spanish

For the driver in a tar.gz file: Chinese (Simplified) | Chinese (Traditional) | English (United States) | French | German | Italian | Japanese | Korean | Portuguese (Brazil) | Russian | Spanish
Microsoft JDBC Driver 4.2 for SQL Server is fully compliant with JDBC specifications 4.1 and 4.2. The jars in the 4.2 package are named according to their compliance with the JDBC API version. For example, the sqljdbc42.jar file from the 4.2 package is JDBC API 4.2 compliant. Similarly, the sqljdbc41.jar file is compliant with JDBC API 4.1.
To ensure you have the right sqljdbc42.jar or sqljdbc41.jar file, run the following lines of code. If the output is "Driver version: 4.2.6420.100", you have the JDBC Driver 4.2 package.
Connection conn = DriverManager.getConnection("jdbc:sqlserver://<server>;encrypt=true;user=<user>;password=<password>;");
System.out.println("Driver version: " + conn.getMetaData().getDriverVersion());
Support for JDK 8
The driver supports JDK version 8.0 in addition to JDK 7.0, 6.0, and 5.0.
JDBC 4.1 and 4.2 compliance
The driver supports Java Database Connectivity API 4.1 and 4.2 specifications, in addition to 4.0. For details, see JDBC 4.1 compliance for the JDBC Driver and JDBC 4.2 compliance for the JDBC Driver.
Bulk copy
You use the bulk copy feature to quickly copy large amounts of data into tables or views in SQL Server databases. For details, see Using bulk copy with the JDBC Driver.
XA transaction rollback option
The driver has new timeout options for existing automatic rollback of unprepared transactions. For details, see Understanding XA transactions.
New Kerberos principal connection property
The driver uses a new connection property to facilitate flexibility with Kerberos connections. For details, see Using Kerberos Integrated Authentication to connect to SQL Server.
Version number: 4.1.8112

Released: December 12, 2014
Support for JDK 7
The driver supports JDK version 7.0 in addition to JDK 6.0 and 5.0.
Itanium not supported for JDBC Driver applications
Microsoft JDBC Driver for SQL Server isn't supported on Itanium computers.
See also
Overview of the JDBC Driver