Early technical preview of JDBC 6.1.4 for SQL Server released!

We are excited to release another early technical preview of the JDBC Driver for SQL Server. The focus of this preview release was enabling Azure Active Directory authentication on Linux, improving the FIPS experience, and adding methods committed in community contributions. Precompiled binaries are available on GitHub here and also on Maven Central.

Below is a summary of the new additions to the project, changes made, and issues fixed.


  • Added isWrapperFor methods for MetaData classes #94
  • Added Code Coverage #136
  • Added TVP schema test #137
  • Introduced FIPS boolean property #135
  • Added unit statement test cases #147


  • Getting TVP name from ParameterMetaData when using TVP with a stored procedure #138
  • Enabled AAD Authentication with Access Token on Linux #142
  • Enabled AAD Authentication with ActiveDirectoryPassword on Linux #146
  • Made Azure Key Vault and Azure Active Directory Authentication Dependencies optional #148

Fixed Issues

  • Fixed getBinaryStream issue #133
  • Fixed an issue of Bulk Copy when AlwaysEncrypted is enabled on connection and destination table is not encrypted #151

Getting the Preview Refresh
The latest bits are available on our GitHub repository and Maven Central.

Add the JDBC preview driver to your Maven project by adding the following code to your POM file to include it as a dependency in your project.


We provide limited support while in preview. Should you run into any issues, please file an issue on our GitHub Issues page.

As always, we welcome contributions of any kind. We appreciate everyone who has taken the time to contribute to the project thus far.

Check out our new tutorials to get started with developing apps in your programming language of choice and SQL Server.

Andrea Lam (andrela@microsoft.com)

Comments (2)

  1. David Frankson says:

    Do your short term plans include implementing Statement Pooling? We were looking to switch from jtds to the MS driver but can’t due to performance problems.

    A comment from a previous release summarized this need perfectly, I’m just going to copy paste it:

    December 1, 2015 at 4:47 pm
    Hello JDBC Team,

    I am the principal developer of HikariCP (github.com/…/HikariCP), the fastest growing connection pool for Java.

    We frequently are asked to implement PreparedStatement caching within the pool, but our stance has always been and continues to be that caching belongs in the driver. On behalf of our MS SQL Server users, I would like to request the implementation of PreparedStatement caching.

    A survey of the Top 5 databases (dzone.com/…/10-most-popular-db-engines-sql) leaves only SQL Server out without prepared statement caching.

    Ironically, SQL Server’s JDBC driver has a property, disableStatementPooling, which defaults to *true. Only true is supported currently (setting to false will throw an exception).

    It was literally HikariCP’s stand against placing responsibility of caching in the pool that prompted PostgreSQL to implement their very excellent solution (github.com/…/308).

    The PostgreSQL implementation took one developer 3 days from start to finish.

    In this new Satya Nadella era, isn’t this the time for Microsoft to prove that it can be just as agile as the open source databases? The 6.0 Preview is the perfect chance to introduce this long needed feature.


    Brett Wooldridge

    1. Andrea Lam says:

      Hi David,

      Thanks for opening an issue on the JDBC GitHub repository as well. Will continue to follow up with you there: https://github.com/Microsoft/mssql-jdbc/issues/166

      Andrea Lam
      Program Manager

Skip to main content