FIX: The result set is returned very slowly when you use the ResultSet object that is included in the SQL Server 2005 JDBC Driver 1.1 (925050)



The information in this article applies to:

  • Microsoft SQL Server 2005 Java Database Connectivity Driver

Bug #: 50000238 (SQL Hotfix)
Bug #: 478596 (SQLBUDT)
Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.

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

Consider the following scenario. In an application, you use the ResultSet object that is included in the Microsoft SQL Server 2005 JDBC Driver version 1.1. You use a SELECT statement to query data. In this scenario, the result set is returned very slowly.

This problem occurs if the following conditions are true:
  • The SELECT statement includes some character columns of the CHAR data type or of the VARCHAR data type.
  • In the application, you specify the SelectMethod=cursor property for the connection.
  • In the application, you set a small fetch size for the connection.
  • The result set contains many rows.
  • You specify one of the SQL collations for the non-Unicode character columns. For example, you specify the SQL_Latin1_General_CP850_CI_AI SQL collation for the CHAR data type columns.

CAUSE

This problem occurs because the SQL Server 2005 JDBC Driver 1.1 makes several costly calls to the Charset.isSupported function. The SQL Server 2005 JDBC Driver 1.1 does this to determine the character set that is associated with a given collation. Specifically, this problem occurs when many character sets are installed for the Java virtual machine.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2005 JDBC Driver 1.1 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

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 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 nameFile versionFile sizeDateTimePlatform
Sqljdbc.jarNot Applicable253,28611-Sep-200609:47Not Applicable
Sqljdbc_auth.dllNot Applicable99,12011-Sep-200604:21x64
Sqljdbc_auth.dllNot Applicable76,59211-Sep-200604:21x86
Xa_install.sqlNot Applicable2,97906-Sep-200602:13Not Applicable
Sqljdbc_xa.dll1.1.1501.200131,37611-Sep-200604:21x64
Sqljdbc_xa.dll1.1.1501.200100,14411-Sep-200604:21x86

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about a related issue in the Java virtual machine, visit the following Sun Microsystems Web site: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

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, regarding the performance or reliability of these products.

Modification Type:MajorLast Reviewed:10/4/2006
Keywords:kbExpertiseAdvanced kbfix kbQFE kbhotfixserver kbpubtypekc KB925050 kbAudDeveloper kbAudITPRO