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
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.
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:
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 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.
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, submit a request to 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.
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:
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.
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:
Start SQL Server Enterprise Manager.
Right-click the instance of SQL Server, and then click Properties.
Click the General tab, and then click Startup Parameters.
In the Startup Parameters dialog box, type -T9068 in the Parameter box, click Add, and then click OK.
In the SQL Server Properties dialog box, click OK.
Restart SQL Server.
For more information, click the following article number to view the article in the Microsoft Knowledge Base: