FIX: A query may run more slowly against SQL Server 2000 post-SP3 hotfix build 8.00.0988 than a query that you run against SQL Server 2000 post-SP3 hotfix builds that are earlier than build 8.00.0988 (911677)


The information in this article applies to:

  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000 Standard Edition
Bug #: 474778 (SQL Server 8.0)
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 this hotfix package
  • The prerequisites for installing the hotfix package
  • Information about whether you must restart the computer after you install the hotfix package
  • Information about whether the hotfix package is replaced by any other hotfix package
  • Information about whether you must make any registry changes
  • The files that are contained in the hotfix package

SYMPTOMS

When you run a query against Microsoft SQL Server 2000 post-Service Pack 3 (SP3) hotfix build 8.00.0988, the query may run more slowly than a query that you run against SQL Server 2000 post-SP3 hotfix builds that are earlier than build 8.00.0988.

This problem also occurs when you run queries against Microsoft SQL Server 2000 post-Service Pack 4 (SP4) hotfix builds.

This problem occurs when all the following conditions are true:
  • The query references a view.
  • The definition of the view contains both a UNION ALL clause and an ORDER BY clause.
For a list of all publicly released SQL Server 2000 Post-Service Pack 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 SP4

CAUSE

This problem occurs because of a change to a cardinality estimate when SQL Server 2000 optimizes the query plan.

RESOLUTION

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

http://support.microsoft.com/contactus/?ws=support

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

You must have Microsoft SQL Server 2000 Service Pack 4 (SP4) installed to apply this hotfix.

For more information about how to obtain SQL Server 2000 Service Pack 4, 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 after you apply this hotfix.

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.32-bit hotfix
File nameFile versionFile sizeDateTimePlatform
Dtsui.dll2000.80.2175.01,593,34402-Dec-200507:54x86
Impprov.dll2000.80.2175.0102,40002-Dec-200507:54x86
Mssdi98.dll8.11.50523.0239,10406-Jun-200521:46x86
Ntwdblib.dll2000.80.2175.0290,81602-Dec-200507:54x86
Odsole70.dll2000.80.2175.069,63202-Dec-200507:54x86
Osql.exe2000.80.2039.057,34402-Dec-200509:51x86
Pfclnt80.dll2000.80.2175.0430,08002-Dec-200507:54x86
Procsyst.sqlNot Applicable552,06816-Jun-200523:15Not Applicable
Replprov.dll2000.80.2175.0237,56802-Dec-200507:54x86
Semexec.dll2000.80.2175.0856,06402-Dec-200507:54x86
Sp4_serv_qfe.sqlNot Applicable18,81016-Jun-200523:15Not Applicable
Sqlagent.exe2000.80.2175.0323,58401-Dec-200519:04x86
Sqldiag.exe2000.80.2175.0118,78401-Dec-200519:42x86
Sqldmo.dll2000.80.2175.04,362,24002-Dec-200507:54x86
Sqlevn70.rll2000.80.2175.045,05602-Dec-200507:54Not Applicable
Sqlfth75.dll2000.80.2175.0102,40001-Dec-200519:11x86
Sqlservr.exe2000.80.2175.09,162,75202-Dec-200507:53x86
Sqlsort.dll2000.80.2175.0589,82402-Dec-200507:54x86
Stardds.dll2000.80.2175.0176,12802-Dec-200507:54x86
Svrnetcn.dll2000.80.2175.0110,59202-Dec-200507:54x86
Ums.dll2000.80.2175.035,32802-Dec-200507:54x86
64-bit hotfix
File nameFile versionFile sizeDateTimePlatform
Dtsui.dll2000.80.2175.01,593,34402-Dec-200507:54x86
Impprov.dll2000.80.2175.0102,40002-Dec-200507:54x86
Mssdi98.dll8.11.50523.0239,10406-Jun-200521:46x86
Ntwdblib.dll2000.80.2175.0290,81602-Dec-200507:54x86
Odsole70.dll2000.80.2175.069,63202-Dec-200507:54x86
Osql.exe2000.80.2039.057,34402-Dec-200509:51x86
Pfclnt80.dll2000.80.2175.0430,08002-Dec-200507:54x86
Procsyst.sqlNot Applicable552,06816-Jun-200523:15Not Applicable
Replprov.dll2000.80.2175.0237,56802-Dec-200507:54x86
Semexec.dll2000.80.2175.0856,06402-Dec-200507:54x86
Sp4_serv_qfe.sqlNot Applicable18,81016-Jun-200523:15Not Applicable
Sqlagent.exe2000.80.2175.0323,58401-Dec-200519:04x86
Sqldiag.exe2000.80.2175.0118,78401-Dec-200519:42x86
Sqldmo.dll2000.80.2175.04,362,24002-Dec-200507:54x86
Sqlevn70.rll2000.80.2175.045,05602-Dec-200507:54Not Applicable
Sqlfth75.dll2000.80.2175.0102,40001-Dec-200519:11x86
Sqlservr.exe2000.80.2175.09,162,75202-Dec-200507:53x86
Sqlsort.dll2000.80.2175.0589,82402-Dec-200507:54x86
Stardds.dll2000.80.2175.0176,12802-Dec-200507:54x86
Svrnetcn.dll2000.80.2175.0110,59202-Dec-200507:54x86
Ums.dll2000.80.2175.035,32802-Dec-200507:54x86
64-bit hotfix for Itanium processors
File nameFile versionFile sizeDateTimePlatform
Impprov.dll2000.80.2175.0244,73602-Dec-200512:46Not Applicable
Mssdi98.dll8.11.50523.0758,78402-Dec-200512:46Not Applicable
Msvcr71.dll7.10.3052.4348,16002-Dec-200512:46Not Applicable
Odsole70.dll2000.80.2175.0150,52802-Dec-200512:46Not Applicable
Pfclnt80.dll2000.80.2175.01,187,84002-Dec-200512:46Not Applicable
Pfclnt80.dll2000.80.2175.0430,08002-Dec-200512:46Not Applicable
Procsyst.sqlNot Applicable552,06802-Dec-200512:46Not Applicable
Replprov.dll2000.80.2175.0538,62402-Dec-200512:46Not Applicable
Replprov2.dll2000.80.2175.0538,62402-Dec-200512:46Not Applicable
Sqlagent.exe2000.80.2175.01,061,37602-Dec-200512:46Not Applicable
Sqldiag.exe2000.80.2175.0334,33602-Dec-200512:46Not Applicable
Sqldmo.dll2000.80.2175.04,362,24002-Dec-200512:46Not Applicable
Sqldmo.dll2000.80.2175.013,860,35202-Dec-200512:46Not Applicable
Sqlevn70.rll2000.80.2175.035,32802-Dec-200512:46Not Applicable
Sqlfth75.dll2000.80.2175.0246,78402-Dec-200512:46Not Applicable
Sqlservr.exe2000.80.2175.024,930,81602-Dec-200512:46Not Applicable
Sqlservr.pdbNot Applicable21,138,43202-Dec-200512:46Not Applicable
Sqlsort.dll2000.80.2175.0617,47202-Dec-200512:46Not Applicable
Svrnetcn.dll2000.80.2175.0427,52002-Dec-200512:46Not Applicable

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, you must have trace flag 9068 turned on when you start SQL Server. If you do not have trace flag 9068 turned on when you start SQL Server, this problem will still occur.

To turn on trace flag 9068, follow these steps:
  1. Start SQL Server Enterprise Manager.
  2. Right-click the instance of SQL Server, and then click Properties.
  3. Click the General tab, and then click Startup Parameters.
  4. In the Startup Parameters dialog box, type -T9068 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, 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

Modification Type:MinorLast Reviewed:7/26/2006
Keywords:kbHotfixServer kbBug kbfix kbtshoot kbQFE kbpubtypekc KB911677 kbAudITPRO kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.