Compartilhar via

Preview the new Microsoft JDBC Driver 6.0 for SQL Server

  • Artigo

Today, we are pleased to announce the availability of the Community Technology Preview (CTP) of the Microsoft JDBC 6.0 Driver for SQL Server! This new driver now supports Always Encrypted, Internationalized Domain Names, Parameterized Queries, and is fully compliant with JDBC specifications 4.1 and 4.2.

To read the full release communication, you can click here.

JDBC Driver Version

JRE Versions

JDBC API Version

6.0

1.5, 1.6, 1.7, 1.8

3.0, 4.0, 4.1, 4.2

The driver can be downloaded from the Microsoft Download Center.

For additional details, check out the SQL Server Developer Center.

We are continuing to work on more exciting features. Please stay tuned for future announcements.

Andrea Lam (andrela@microsoft.com)

Comments

  • Anonymous
    November 10, 2015
    Still no bulk copy or TVP support? When are we going to get these? They are absolutely key for performance, scalability, and decent code.

  • Anonymous
    November 10, 2015
    TVP support is an absolute necessity. I'm working with a client who's trying to do a migration from Oracle, is this is a blocker.

  • Anonymous
    November 11, 2015
    @Adam, I just did some checking and it seems that they did add support for Bulk Copy in v 4.2. There is documentation ( msdn.microsoft.com/.../mt221490.aspx ) and an announcement of it ( msdn.microsoft.com/.../aa342325.aspx ). But yeah, sadly still no support for TVPs :-(

  • Anonymous
    November 12, 2015
    How can we push BLOB & CLOB data (more than 8K in size) from Oracle to SQL Server using the new SQLServerBulkCopy class introduced in ver 4.2?

  • Anonymous
    November 12, 2015
    The current version of JDBC 4.2 is not working with JRE 6 and 7, though as per the documentation it should. By when we can except a version which supports JRE 6,7 and 8?

  • Anonymous
    November 12, 2015
    @Adam, as Solomon mentioned, Bulk Copy support was added in v4.2. This feature is also available in this preview driver. We know that TVP support is important and it is currently in the works for our upcoming releases. Thanks, Andrea Lam Program Manager

  • Anonymous
    November 14, 2015
    Disappointed with not seeing TVP support too.

  • Anonymous
    November 15, 2015
    Can someone please revert back to the queries raised by me.

  • Anonymous
    December 01, 2015
    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. Regards, Brett Wooldridge

  • Anonymous
    December 18, 2015
    How about putting it Maven Central?

  • Anonymous
    December 22, 2015
    I'm very disappointed too, waiting for TVP support :(

  • Anonymous
    January 05, 2016
    When will DatabaseMetadata.getTables properly support synonyms? Since SQL Server added support at the database level the client API support has been lacking.

  • Anonymous
    January 06, 2016
    Any idea when the JDBC Driver 6.0 will be GA? It fixed an existing v4.2 bug that our test cases encountered. We would like to certify the MSFT JDBC driver for our product, but that's on-hold until v6.0 is officially released.

  • Anonymous
    January 08, 2016
    @Rajesh Ag: Can you please provide more details regarding JDBC Driver v4.2 not working with JRE 6, 7, and 8? @Brett Wooldridge: Thank you for your feedback. I agree with you that the PreparedStatement caching belongs to the client driver. We will review and prioritize this against other requests and move forward accordingly. I will update this thread when we have a more concrete plan. @the6campbells: We will review and prioritize the request. I will update you as we make progress. Thanks, Andrea Lam Program Manager

  • Anonymous
    January 15, 2016
    @Andrea Lam - How do we open a bug report or support ticket against the Microsoft JDBC driver?

  • Anonymous
    January 18, 2016
    The comment has been removed

  • Anonymous
    January 19, 2016
    On the wire compression would help in some use cases particularly bulk/batch transfers.

  • Anonymous
    January 19, 2016
    @Peter Tran: You can report a bug through the MS Connect tool (https://connect.microsoft.com/) @John Lonergan: Thank you for your feedback. Let me see what I can do to help provide more extensive documentation on the BulkCopy APIs. Thanks, Andrea Lam (andrela@microsoft.com) Program Manager

  • Anonymous
    February 10, 2016
    Any plans on fixes for two major issues holding us and the rest from the world from using the JDBC driver? 1.) Provide an option to set the socket timeout. See the discussion at social.technet.microsoft.com/.../any-plans-to-add-socket-timeout-option-in-jdbc-driver The current implementation will lead to stuck threads on packet loss, which eventually kills your appserver. At least that was the case for 4.2, and I assume it is still the case for 6.0. 2.) Use a proper license (MIT / Apache 2 / BSD)

    • Anonymous
      July 14, 2016
      Hi Mike,We have heard a number of users ask for this functionality. We are prioritizing this implementation against several other features. Please be on the look out for more announcements in the future. We hope to address this issue soon. Thanks,Andrea LamProgram Managerandrela@microsoft.com

  • Anonymous
    February 28, 2016
    @Andrea Lam: the driver classes were compiled with the -target 1.8 flag so the classes have a major.minor version of 52.0 which makes them only usable in Java 8 runtimes.

  • Anonymous
    April 04, 2016
    Any chance we could get (https://connect.microsoft.com/SQLServer/feedback/details/2280301) fixed? It locks up the DBMS :-(.

  • Anonymous
    June 17, 2016
    Doesn't seem to represent any monetisable intellectual property? Might even result in a more complete product.

    • Anonymous
      July 14, 2016
      Hi John, This is definitely something to consider. We are working on some exciting things in our subsequent releases. Please stay tuned for further announcements. Thanks,Andrea Lam Program Manager andrela@microsoft.com