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.
If you are a Small Business customer, find additional troubleshooting and learning resources at the Support for Small Business site.
Consider the following scenario. You upgrade from Microsoft SQL Server 2000 Service Pack 3 (SP3) to Microsoft SQL Server 2000 Service Pack 4 (SP4). Then, you run a query that uses the UNION ALL operator. In this scenario, you may notice a decrease in performance.
This problem may occur if the following conditions are true:
You query data from joined tables.
The joined tables contain columns that use constraints.
The joined tables contain lots of records.
Additionally, this problem occurs in the original release version of SQL Server 2000, in SQL Server 2000 build 8.00.850, and in SQL Server 2000 builds later than build 8.00.850.
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.
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:
How to obtain the latest SQL Server 2000 service pack
You do not have to restart the computer after you apply this hotfix.
You do not have 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.
Description of the standard terminology that is used to describe Microsoft software updates
Steps to reproduce the problem
In SQL Server 2000 SP4, run the following statements by using SQL Query Analyzer.
create database repro
create table t1 (i int constraint pkt1 primary key check ((i>11) and (i< 15)), j int )
create table t2 (a int constraint pkt2 primary key check ((a>15) and (a< 20)), b int)
create table t3 (c int constraint pkt3 primary key check ((c>7) and (c< 13)), d int)
create table t4 (e int constraint pkt4 primary key check ((e>19) and (e< 24)), f int)
create table s1 (i int constraint pkt5 primary key, j int)
create table s2 (a int constraint pkt6 primary key, b int)
create table s3 (c int constraint pkt7 primary key, d int)
create table s4 (e int constraint pkt8 primary key, f int)
create view v1 as
select t1.* from
t1 inner join s1 on t1.i = s1.i
select t2.* from
t2 inner join s2 on t2.a = s2.a
create view v2 as
select t3.* from
t3 inner join s3 on t3.c = s3.c
select t4.* from
t4 inner join s4 on t4.e = s4.e
To make SQL Server return execution information, run the following statements.
set showplan_text on
Run the following statements, and then examine the output.
select * from v1 inner join v2 on i = c
where i = 12 or i = 17
The following inefficient execution plan is displayed in the output.