Microsoft KB Archive/919133

From BetaArchive Wiki

Article ID: 919133

Article Last Modified on 11/2/2007



APPLIES TO

  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000 Workgroup Edition



Bug #: 757 (SQL Hotfix)
Bug #: 50000199 (SQL Hotfix)

Microsoft distributes Microsoft SQL Server 2000 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 2000 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 you must make any registry changes
  • The files that are contained in the hotfix package


SYMPTOMS

Consider the following scenario:

  • In Microsoft SQL Server 2000, you execute a single query, or you execute multiple concurrent queries.
  • Each query returns several levels of nested derived tables.
  • Each derived table contains aggregations.

In this scenario, you may experience the following symptoms:

  • Each query takes a long time to compile.
  • The SQL Server scheduler stops responding (hangs).
  • The computer that is running SQL Server consistently has high CPU utilization.
  • Several error messages are logged in the SQL Server error log. These error messages have error code 17883.


Note The system server process ID (SPID) for these error messages corresponds to the SPID of the single query or to the SPIDs of the multiple concurrent queries.

For a list of all publicly released SQL Server 2000 post-Service Pack 4 hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:

894905 Cumulative list of the hotfixes that are available for SQL Server 2000 Service Pack 4


RESOLUTION

The installer does not install this hotfix correctly on x64-based systems. This installation issue occurs when the following conditions are true:

  • The system uses the Advanced Micro Devices (AMD) AMD64 processor architecture or the Intel Extended Memory 64 Technology (EM64T) processor architecture.


Note This issue does not occur on systems that use the Intel Itanium processor architecture.

  • The system is running a 64-bit version of the Microsoft Windows Server operating system.
  • The system is running a 32-bit version of SQL Server 2000.

We have corrected this installation issue in later builds of SQL Server 2000, starting with version 8.00.2244. When a customer who is running SQL Server 2000 on an x64-based system requests this hotfix, we will provide a build that includes this hotfix and that can be installed correctly on an x64-based system. The build that we provide will be version 8.00.2244 or a later version.

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 2000 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

  • Microsoft SQL Server 2000 Service Pack 4 (SP4)

    For information about how to obtain SQL Server 2000 SP4, click the following article number to view the article in the Microsoft Knowledge Base:

    290211 How to obtain the latest SQL Server 2000 service pack

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.

SQL Server 2000, 32-bit hotfix
File name File version File size Date Time Platform
Dtsui.dll 2000.80.2197.0 1,593,344 16-May-2006 15:22 x86
Impprov.dll 2000.80.2197.0 102,400 16-May-2006 15:22 x86
Msgprox.dll 2000.80.2197.0 94,208 16-May-2006 15:22 x86
Msrpjt40.dll 4.10.9424.0 188,473 24-Jan-2006 08:13 x86
Mssdi98.dll 8.11.50523.0 239,104 06-Jun-2005 22:46 x86
Ntwdblib.dll 2000.80.2197.0 290,816 16-May-2006 15:22 x86
Odsole70.dll 2000.80.2197.0 69,632 16-May-2006 15:22 x86
Osql.exe 2000.80.2197.0 57,344 16-May-2006 00:35 x86
Pfclnt80.dll 2000.80.2197.0 430,080 16-May-2006 15:22 x86
Replmerg.exe 2000.80.2197.0 163,840 16-May-2006 00:45 x86
Replprov.dll 2000.80.2197.0 237,568 16-May-2006 15:22 x86
Replrec.dll 2000.80.2197.0 315,392 16-May-2006 15:22 x86
Replsub.dll 2000.80.2197.0 270,336 16-May-2006 15:22 x86
Semexec.dll 2000.80.2197.0 856,064 16-May-2006 15:22 x86
Sqlagent.exe 2000.80.2197.0 323,584 16-May-2006 00:10 x86
Sqldiag.exe 2000.80.2197.0 118,784 16-May-2006 01:57 x86
Sqldmo.dll 2000.80.2197.0 4,362,240 16-May-2006 15:22 x86
Sqlfth75.dll 2000.80.2197.0 102,400 16-May-2006 00:31 x86
Sqlservr.exe 2000.80.2197.0 9,162,752 16-May-2006 04:44 x86
Sqlsort.dll 2000.80.2197.0 589,824 16-May-2006 15:22 x86
Stardds.dll 2000.80.2197.0 176,128 16-May-2006 15:22 x86
Svrnetcn.dll 2000.80.2197.0 110,592 16-May-2006 15:22 x86
Ums.dll 2000.80.2197.0 35,328 16-May-2006 15:22 x86
Xpstar.dll 2000.80.2197.0 311,296 16-May-2006 15:22 x86


WORKAROUND

To work around this problem, rewrite the queries to reduce the number of derived tables or to reduce the number of aggregations.

STATUS

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

MORE INFORMATION

After you apply this hotfix, trace flag 222 must be turned on when you start SQL Server. If trace flag 222 is not turned on when you start SQL Server, this problem still occurs. To turn on trace flag 222, follow these steps:

  1. Start SQL Server Enterprise Manager.
  2. Right-click the instance of SQL Server, and then click Properties.
  3. On the General tab, click Startup Parameters.
  4. In the Startup Parameters dialog box, type -T222 in the Parameter box, click Add, and then click OK.
  5. In the SQL Server Properties dialog box, click OK.
  6. Restart SQL Server.

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


For more information about this problem, click the following article number to view the article in the Microsoft Knowledge Base:

891866 FIX: The query runs slower than you expected when you try to parse a query in SQL Server 2000


Stack information

When this problem occurs, you may receive the following stack dump information:

sqlservr!a_remapvar+0xbb
sqlservr!a_remapvar+0x12a
sqlservr!a_remapvar+0x12a
sqlservr!a_remapvar+0x145
sqlservr!a_remapvar+0x19f
sqlservr!a_remapvar+0x177
sqlservr!a_remapvar+0x20a
sqlservr!a_remapvar+0x20a
sqlservr!a_remapvar+0x12a
sqlservr!a_remapvar+0x12a
sqlservr!a_remapvar+0x145
sqlservr!a_remapvar+0x12a
sqlservr!a_remapvar+0x12a
sqlservr!a_remapvar+0x177
sqlservr!a_remapvar+0x20a
sqlservr!a_remapvar+0x145
sqlservr!a_remapvar+0x20a
sqlservr!a_remapvar+0x177
sqlservr!a_remapvar+0x20a
sqlservr!a_remapvar+0x12a
sqlservr!a_remapvar+0x145
sqlservr!a_remapvar+0x145
sqlservr!a_remapvar+0x145
sqlservr!a_remapvar+0x12a
sqlservr!a_remapvar+0x145
sqlservr!a_remapvar+0x177
sqlservr!res_remapvar+0x45
sqlservr!res_derived+0x358
sqlservr!res_view+0x68a
sqlservr!CCompPlan::FPreprocess+0x82
sqlservr!CCompPlan::FCompileStep+0x7f6
sqlservr!CProchdr::FCompile+0x111f
sqlservr!CSQLSource::FTransform+0x395
sqlservr!CSQLStrings::FTransform+0x21a
sqlservr!CSQLSource::Execute+0x178
sqlservr!language_exec+0x451
sqlservr!process_commands+0x13f
ums!ProcessWorkRequests+0x2d9
ums!ThreadStartRoutine+0x98
msvcr71!_threadstart+0x6c
kernel32!BaseThreadStart+0x37

Keywords: kbexpertiseadvanced kbbug kbfix kbtshoot kbhotfixserver kbqfe kbpubtypekc KB919133