We recommend that you unpack the compressed (.zip) files by using the following default directory: When you are prompted, enter an installation directory.
To accept this license agreement, download and use Microsoft SQL Server JDBC Driver version 3.0.ĭownload and save the sqljdbc_enu.exe file in a temporary directory. Read the license.txt file for this hotfix.
To install this hotfix, follow these steps. If you do not see your language, it is because a hotfix is not available for that language. The "Hotfix download available" form displays the languages for which the hotfix is available. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article.
Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix. 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 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