FIX: Each query takes a long time to compile when you execute a single query or when you execute multiple concurrent queries in SQL Server 2000 (919133)



The information in this article 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

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 nameFile versionFile sizeDateTimePlatform
Dtsui.dll2000.80.2197.01,593,34416-May-200615:22x86
Impprov.dll2000.80.2197.0102,40016-May-200615:22x86
Msgprox.dll2000.80.2197.094,20816-May-200615:22x86
Msrpjt40.dll4.10.9424.0188,47324-Jan-200608:13x86
Mssdi98.dll8.11.50523.0239,10406-Jun-200522:46x86
Ntwdblib.dll2000.80.2197.0290,81616-May-200615:22x86
Odsole70.dll2000.80.2197.069,63216-May-200615:22x86
Osql.exe2000.80.2197.057,34416-May-200600:35x86
Pfclnt80.dll2000.80.2197.0430,08016-May-200615:22x86
Replmerg.exe2000.80.2197.0163,84016-May-200600:45x86
Replprov.dll2000.80.2197.0237,56816-May-200615:22x86
Replrec.dll2000.80.2197.0315,39216-May-200615:22x86
Replsub.dll2000.80.2197.0270,33616-May-200615:22x86
Semexec.dll2000.80.2197.0856,06416-May-200615:22x86
Sqlagent.exe2000.80.2197.0323,58416-May-200600:10x86
Sqldiag.exe2000.80.2197.0118,78416-May-200601:57x86
Sqldmo.dll2000.80.2197.04,362,24016-May-200615:22x86
Sqlfth75.dll2000.80.2197.0102,40016-May-200600:31x86
Sqlservr.exe2000.80.2197.09,162,75216-May-200604:44x86
Sqlsort.dll2000.80.2197.0589,82416-May-200615:22x86
Stardds.dll2000.80.2197.0176,12816-May-200615:22x86
Svrnetcn.dll2000.80.2197.0110,59216-May-200615:22x86
Ums.dll2000.80.2197.035,32816-May-200615:22x86
Xpstar.dll2000.80.2197.0311,29616-May-200615:22x86

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

Modification Type:MajorLast Reviewed:8/2/2006
Keywords:kbExpertiseAdvanced kbBug kbfix kbtshoot kbQFE kbhotfixserver kbpubtypekc KB919133 kbAudITPRO kbAudDeveloper