This hotfix might receive additional testing. Apply this hotfix only to systems that are experiencing the problem described in this article. However, this hotfix is intended to correct only the problem that is described in this article.
Microsoft sql server jdbc driver 3.0 driver#
Microsoft JDBC Driver 4.0 for SQL Server will also contain this modification.Ī supported hotfix is available from Microsoft. Microsoft SQL Server JDBC Driver version 3.0 was modified so that the functions that are described in the "Symptoms" section return correct values regardless of the JRE version. Because of changes in the behavior of these APIs, Microsoft SQL Server JDBC Driver version 3.0 returns incorrect values. The behavior of the functions that are described in the "Symptoms" section depends on the Java calendar APIs. Microsoft SQL Server JDBC Driver version 2.0 and JRE 1.7 Microsoft SQL Server JDBC Driver version 3.0 and JRE 1.5 or JRE 1.6 This issue does not occur if the application uses one of the following combinations of components: This issue occurs only when the date value that is returned by the function is more recent than the year 1582 in the Gregorian calendar. In this scenario, the function returns an incorrect date value. The data type in the SQL Server database is DATE, DATETIME2, or DATETIMEOFFSET. The application uses any of the following functions to obtain a date from the database: You have a Java application that uses Microsoft SQL Server JDBC Driver version 3.0 and Java Runtime Environment version 1.7 (JRE 1.7) to connect to a SQL Server database. KB2652061 - FIX: SQL Server JDBC Driver 3.0 returns incorrect date values when used with JRE 1.7 by a Java application Symptoms