Partager via

Hotfix Available for Date Issue When Using JRE 1.7

  • Article

Dear SQL Server developers and users:

Thank you for your ongoing support of the Microsoft JDBC Driver for SQL Server.  Some of you reported problems with dates when using JRE 1.7.

The Microsoft JDBC Driver for SQL Server currently supports JRE 1.5 & JRE 1.6, however we have made modifications to return correct date values regardless of the JRE version. This modification is available in the production version of the Microsoft JDBC Driver 4.0 for SQL Server.  The Microsoft JDBC Driver 4.0 for SQL Server
is supported on JRE 1.5 and JRE 1.6, and support for JRE 1.7 is on our roadmap.

In addition, the driver modification is also available for SQL Server 2000 customers as a hotfix in the 3.0 version of our driver. Please review the hotfix article to determine if the fix is applicable to you and if so, click the link to download the hotfix (applicable for all platforms).

As always we are interested in your feedback. You may report bugs and issues via our forums. If you encounter Java bugs you may report those to Java.

Thank you,
Shamitha Reddy
Program Manager Microsoft JDBC Driver for SQL Server

For technical support, please use our forums.

Comments

  • Anonymous
    February 17, 2012
    Hi, You should take into account the end of live of the different version of the JRE.  End of this year no more update of Java SE 6 will be available for non subscriber of a commercial life extension. You can find more information here: www.oracle.com/.../eol-135779.html

  • Anonymous
    February 17, 2012
    @Francois Thanks for the feedback.  We are aware that JRE SE 6 is going end of life so we have added JRE 1.7 support to our roadmap.

  • Anonymous
    April 18, 2012
    This does not seem to work with version 4 of the driver.

  • Anonymous
    April 18, 2012
    @Sam Ratcliff We tested the 3.0 and 4.0 versions of our driver extensively with the date fix.  Can you provide more details so we can reproduce your issue and understand if the behaviour you see is a regression or perhaps a new issue? Please open a Microsoft Connect case and include details on your driver version, Java version and update number, operating system, SQL Server version and code to reproduce your issue. Link to Connect site - connect.microsoft.com/.../Feedback