|
 |
 |
 |
 |
Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms
of Use |
Trademarks
Article ID: 917055 - Last Review: October 9, 2011 - Revision: 2.0 FIX: The SQL Server 2005 JDBC Driver may not return the correct dates when you use the getTimestamp(,,Calendar) method or the setTimestamp(,,Calendar) method in a prepared statementBUG #: 424 (SQL Hotfix) 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 you must make any registry changes
- The files that are contained in the hotfix
package
Consider the following scenario. You use the getTimestamp(,,Calendar) method or the setTimestamp(,,Calendar) method in a prepared statement. The prepared statement runs on a Microsoft SQL Server 2005 JDBC Driver connection. In this scenario, the SQL Server 2005 JDBC Driver may not return the correct dates. Typically,
you experience this problem in geographical areas that are on the boundary of
daylight-saving time. Hotfix information A supported hotfix is 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 software update that contains this hotfix. If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. PrerequisitesThere 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 informationThis hotfix contains only those files that are required to correct
the issues that this article lists. This hotfix may not contain 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. Collapse this tableExpand this table | File name | File version | File
size | Date | Time | Platform |
|---|
| Sqljdbc.jar | Not
Applicable | 221,392 | 10-Mar-2006 | 23:27 | Not
Applicable | | Xa_install.sql | Not
Applicable | 2,987 | 10-Mar-2006 | 23:27 | Not
Applicable | | Sqljdbc_xa.dll | 1.0.809.202 | 71,680 | 10-Mar-2006 | 23:27 | IA-64 | | Sqljdbc_xa.dll | 1.0.809.202 | 41,472 | 10-Mar-2006 | 23:27 | x64 | | Sqljdbc_xa.dll | 1.0.809.202 | 30,208 | 10-Mar-2006 | 23:27 | x86 |
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about JDBC, click the following article number to view the article in the Microsoft Knowledge Base:
313100Â
(http://kbalertz.com/Feedback.aspx?kbNumber=313100/
)
How
to get started with Microsoft JDBC
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684Â
(http://kbalertz.com/Feedback.aspx?kbNumber=824684/
)
Description of the standard terminology that is used to describe
Microsoft software updates
Steps to reproduce the problemCompile and then run the following Java code sample. import java.sql.*;
import java.util.*;
public class SQL2k5 {
public static void main (String[] args) throws Exception{
Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
Connection conn = DriverManager.getConnection("jdbc:sqlserver://<Server>;user=<UserId>;password=<Password>;database=<DatabaseName>");
DatabaseMetaData dbmd = conn.getMetaData();
System.out.println("Driver version is " + dbmd.getDriverVersion() );
Statement stmt = conn.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_UPDATABLE);
try {stmt.executeUpdate("drop table TimeZoneTable");}
catch (Exception e) {}
stmt.executeUpdate("create table TimeZoneTable (col1 datetime)");
ResultSet rs;
TimeZone.setDefault(TimeZone.getTimeZone("America/Los_Angeles"));
System.out.println("My time zone is " + TimeZone.getDefault());
stmt.executeUpdate("insert into TimeZoneTable (col1) values (N'4/2/2006 02:00:00.008')");
rs = stmt.executeQuery("select cast (col1 as char(25)) from TimeZoneTable");
rs.next();
System.out.println("\nTime from database (as string): " + rs.getString(1));
rs = stmt.executeQuery("select col1 from TimeZoneTable");
rs.next();
System.out.println("Returned time with no Calendar: " + rs.getTimestamp(1));
System.out.println("Returned time with America/New_York Calendar: " + rs.getTimestamp(1, Calendar.getInstance(TimeZone.getTimeZone("America/New_York"), Locale.US)));
System.out.println("Returned time with America/Phoenix Calendar: " + rs.getTimestamp(1, Calendar.getInstance(TimeZone.getTimeZone("America/Phoenix"), Locale.US)));
System.out.println("Returned time with America/Denver Calendar: " + rs.getTimestamp(1, Calendar.getInstance(TimeZone.getTimeZone("America/Denver"), Locale.US)));
System.out.println("Returned time with America/Indianapolis Calendar: " + rs.getTimestamp(1, Calendar.getInstance(TimeZone.getTimeZone("America/Indianapolis"), Locale.US)));
System.out.println("Returned time with Pacific/Honolulu Calendar: " + rs.getTimestamp(1, Calendar.getInstance(TimeZone.getTimeZone("Pacific/Honolulu"), Locale.US)));
}
}
Note To use this code sample, replace the following placeholders:
- Replace <Server> by using the name of the instance of SQL
Server.
- Replace <DatabaseName> by using the name of the
database.
- Replace <UserId> by using your user ID.
- Replace <Password> by using your password.
When you run this code sample, you receive the following result: Driver version is 1.0.809.102
My time zone is sun.util.calendar.ZoneInfo[id="America/Los_Angeles",offset=-28800000,dstSavings=3600000,useDaylight=true,transitions=185,lastRule=java.util.SimpleTimeZone[id=America/Los_Angeles,offset=-28800000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=3,startMonth=3,startDay=1,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=2,endMonth=9,endDay=-1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]]
Time from database (as string): Apr 2 2006 2:00AM
Returned time with no Calendar: 2006-04-02 03:00:00.007
Returned time with America/New_York Calendar: 2006-04-01 23:00:00.007
Returned time with America/Phoenix Calendar: 2006-04-02 03:00:00.007
Returned time with America/Denver Calendar: 2006-04-02 01:00:00.007
Returned time with America/Indianapolis Calendar: 2006-04-02 00:00:00.007
Returned time with Pacific/Honolulu Calendar: 2006-04-02 06:00:00.007
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
APPLIES TO- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Java Database Connectivity Driver
| kbautohotfix kbsql2005webdata kbHotfixServer kbqfe KB917055 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
|
 |
 |
 |
 |
 |
 |
 |
| |