Article ID: 936697
Article Last Modified on 11/4/2007
APPLIES TO
- Microsoft SQL Server 2005 Java Database Connectivity Driver
Bug: #50001088 (SQL Hotfix)
SUMMARY
This article describes the following about this hotfix release:
- The issues that are fixed by the hotfix package
- The prerequisites for installing the hotfix package
- Whether you must restart the computer after you install the hotfix package
- Whether the hotfix package is replaced by any other hotfix package
- Whether you must make any registry changes
- The files that are contained in the hotfix package
SYMPTOMS
When you use the getTime method in the Microsoft SQL Server 2005 JDBC Driver 1.1, the method returns an incorrect date. The returned date is always January 1 of the current year.
Note This problem only occurs when you use this driver together with the IBM JVM version 1.4.2. The returned date is correct when you use this driver together with Sun's JDK 1.4.2 and Sun's JDK 1.5.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
There are no prerequisites for this hotfix.
Restart information
You do not have to restart the computer after you apply this hotfix.
Registry information
You do not have to change the registry.
Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Sqljdbc.jar | Not applicable | 254,807 | 26-Apr-2007 | 03:08 | Not applicable |
| Sqljdbc_auth.dll | Not applicable | 101,768 | 26-Apr-2007 | 03:08 | x64 |
| Sqljdbc_auth.dll | Not applicable | 79,240 | 26-Apr-2007 | 03:08 | x86 |
| Xa_install.sql | Not applicable | 2,979 | 24-Apr-2007 | 01:30 | Not applicable |
| Sqljdbc_xa.dll | 1.1.1501.204 | 134,024 | 26-Apr-2007 | 03:08 | x64 |
| Sqljdbc_xa.dll | 1.1.1501.204 | 102,792 | 26-Apr-2007 | 03:08 | x86 |
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
You can use the following code to reproduce the problem when you use the SQL Server 2005 JDBC Driver 1.1 together with the IBM JVM 1.4.2.
public static void Repro426796() throws Exception
{
Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
Connection conn = DriverManager.getConnection("jdbc:sqlserver://ServerName;user=UserName;password=password");
Statement stmt = conn.createStatement();
try {stmt.executeUpdate("drop table t_Repro");} catch (Exception e) {System.out.println(e.toString());}
try {stmt.executeUpdate("create table t_Repro (col1 datetime)");} catch (Exception e) {System.out.println(e.toString());}
try {stmt.executeUpdate("insert into t_Repro (col1) values (N'2006-02-13 18:15:00.007')");} catch (Exception e) {System.out.println(e.toString());}
try {stmt.executeUpdate("insert into t_Repro (col1) values (NULL)");} catch (Exception e) {System.out.println(e.toString());}
try
{
ResultSet rs = stmt.executeQuery("select * from t_Repro");
while (rs.next())
{
System.out.println("Column value as Date: " + rs.getDate(1) + ((null == rs.getDate(1)) ? " null" : " (" + rs.getDate(1).getTime() + ")"));
System.out.println("Column value as Time: " + rs.getTime(1) + ((null == rs.getTime(1)) ? " null" : " (" + rs.getTime(1).getTime() + ")"));
System.out.println("Column value as Timestamp: " + rs.getTimestamp(1) + ((null == rs.getTimestamp(1)) ? " null" : " (" + rs.getTimestamp(1).getTime() + ")"));
Calendar cal = Calendar.getInstance(TimeZone.getTimeZone("America/Denver"));
System.out.println("Column value as Date: " + rs.getDate(1, cal) + ((null == rs.getDate(1, cal)) ? " null" : " (" + rs.getDate(1, cal).getTime() + ")"));
System.out.println("Column value as Time: " + rs.getTime(1, cal) + ((null == rs.getTime(1, cal)) ? " null" : " (" + rs.getTime(1, cal).getTime() + ")"));
System.out.println("Column value as Timestamp: " + rs.getTimestamp(1, cal) + ((null == rs.getTimestamp(1, cal)) ? " null" : " (" + rs.getTimestamp(1, cal).getTime() + ")"));
}
rs.close();
}
catch (Exception e)
{
System.out.println(e.toString());
}
finally
{
try {stmt.executeUpdate("drop table t_Repro");} catch (Exception e) {System.out.println(e.toString());}
}
stmt.close();
conn.close();
}
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
Keywords: kbexpertiseadvanced kbfix kbhotfixserver kbqfe kbpubtypekc KB936697
