Microsoft JDBC Driver 4.0 for SQL Server CTP2 is Released!!!

Dear SQL Server developers and users:

Thank you for providing great feedback on our first Community Technology Preview (CTP) of Microsoft JDBC Driver 4.0 for SQL Server. I am very pleased to announce the availability of our second CTP. This CTP includes bug fixes based on your feedback and additional features in “Denali”.

This release includes:

-      Type-4 Kerberos Integrated Security

  • Support for authentication via TGT in cache
  • Login configuration file support
  • Single sign-on through mid-tier

-      Client side support for SQL Server AlwaysOn Feature for Denali

  • Support for multi-subnet failover for AlwaysOn
  • Support for connecting to read-only replicas for AlwaysOn

-      Support for SQL Azure

Let us know how we’re doing and give us your feedback through the Microsoft SQL Server Data Access Forum, Microsoft Connect, or this blog.


Thank you,

Amina Saify, Program Manager – SQL Server/JDBC

Comments (7)
  1. Franjo Stipanovic - fritz says:

    Dear SQL Server team,

    what do we have to do to get your permission to upload JDBC driver in public Maven repository? This is very important to us because this is the only dependency which I have to manually add into my own local repository.

    Kind regards,


  2. Michael Burman says:

    Still no fix for formatId problem in XA transactions? Could you at least document on where the problem is, MSDTC or the JDBC driver? Since they always return 0 when doing XARecovery process thus rendering the whole transactional behaviour of SQL Server useless with multiple datasources.

  3. Amina says:

    Hi Franjo, thanks for your feedback. We will look into how to get our driver in Maven repository.

    Hi Michael, This is a great feedback. Currently, the driver ignores formatId and always considers it as 0. Please find below a snippet from X/Open CAE Specification (Distributed Transaction Processing: The XA Specification) .

    "The only requirement is that both gtrid and bqual , taken together, must be globally unique. The recommended way of achieving global uniqueness is to use the naming rules specified for OSI CCR atomic action identifiers (see the referenced OSI CCR specification). If OSI CCR naming is used, then the XID’s formatID element should be set to 0"

    We will certainly document the driver behavior.

  4. wesclark says:

    Are there plans to support geodata and geometry datatypes and functionality?

  5. Laszlo Sas says:

    Dear JDBC Driver Team,

    using the driver with large result set consumes the memory of the application server. It does not leak. It uses too much.

    I have used the following connection url:


    If I use the older version (3.0) of the driver the result is the same. It uses too much memory.

    What's wrong with my settings? Or is this a bug?



  6. dpblogs says:

    @Wes Clark

    We currently do not have any plans to support geodata & geometry datatypes in the Microsoft JDBC Driver for SQL Server.  Have you looked into Hibernate Spatial and Java Topology Suite (JTS)?

  7. dpblogs says:

    @Laszlo Sas

    Thanks for your question.  Would it be possible for to post your question on the JDBC Forums so it will be visible to a wider audience including Microsoft?

    Here is the link to the data access forums.…/threads

Comments are closed.

Skip to main content