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
Consider the following scenario. In Microsoft SQL Server 2000, you run a query that uses the ORDER BY clause to sort a column in a table. The table has an index. In this scenario, the result may be sorted in the wrong order.
This problem occurs if one of the following conditions is true:
- The query uses the IN keyword. For example, the query uses the following predicate.
- The query uses a predicate that is equivalent to a predicate that uses the IN keyword. For example, the query uses the following predicate.
(a = 2 or a = 10 or a = 12 or a = 23)
The following examples are examples of this problem:
- In the index definition, a column is sorted in ascending order. You run a query that uses the ORDER BY clause to sort the column in descending order. When you run the query, the result is sorted in ascending order.
- In the index definition, a column is sorted in descending order. You run a query that uses the ORDER BY clause to sort the column in ascending order. When you run the query, the result is sorted in descending order.
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.
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.
To apply this hotfix, you must have SQL Server 2000 Service Pack 4 (SP4) installed.
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
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix is not replaced by any other hotfixes.
You do not have to change the registry.
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.
Collapse this tableExpand this table
|File name||File version||File size||Date||Time||Platform|
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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:
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:
Description of the standard terminology that is used to describe Microsoft software updates