FIX: You may notice a decrease in performance when you run a query that uses the UNION ALL operator in SQL Server 2000 Service Pack 4

Article translations Article translations
Article ID: 917606 - View products that this article applies to.
Bug #: 527 (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.
Expand all | Collapse all

On This Page

SUMMARY

This article describes the following about this hotfix release:
  • The issues that are fixed by the hotfix package
  • The prerequisites for applying the hotfix package
  • Whether you must restart the computer after you apply the hotfix package
  • Whether the hotfix package is replaced by any other hotfix package
  • Whether you must make any registry changes after you apply the hotfix package
  • The files that are contained in the hotfix package

SYMPTOMS

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:
894905 Cumulative list of the hotfixes that are available for SQL Server 2000 Service Pack 4

CAUSE

This problem occurs because SQL Server generates an inefficient execution plan that has redundant cluster index scans.

RESOLUTION

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:
http://support.microsoft.com/contactus/?ws=support
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

  • 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 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 x86 versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
80sp4-tools.sqlNot Applicable134,62819-Feb-200601:40Not Applicable
Dtsui.dll2000.80.2192.01,593,34404-Apr-200606:00x86
Impprov.dll2000.80.2192.0102,40004-Apr-200606:00x86
Msgprox.dll2000.80.2192.094,20804-Apr-200606:00x86
Msrpjt40.dll4.10.9424.0188,47324-Jan-200608:13x86
Mssdi98.dll8.11.50523.0239,10406-Jun-200522:46x86
Ntwdblib.dll2000.80.2192.0290,81604-Apr-200606:00x86
Odsole70.dll2000.80.2192.069,63204-Apr-200606:00x86
Osql.exe2000.80.2192.057,34404-Apr-200602:28x86
Pfclnt80.dll2000.80.2192.0430,08004-Apr-200606:00x86
Procsyst.sqlNot Applicable552,06817-Jun-200500:15Not Applicable
Replmerg.exe2000.80.2192.0163,84004-Apr-200602:49x86
Replmerg.sqlNot Applicable1,151,45004-Apr-200601:56Not Applicable
Replprov.dll2000.80.2192.0237,56804-Apr-200606:00x86
Replrec.dll2000.80.2192.0315,39204-Apr-200606:00x86
Replsub.dll2000.80.2192.0270,33604-Apr-200606:00x86
Repltran.sqlNot Applicable1,000,63402-Feb-200621:59Not Applicable
Semexec.dll2000.80.2192.0856,06404-Apr-200606:00x86
Sp4_serv_qfe.sqlNot Applicable18,81017-Jun-200500:15Not Applicable
Sqlagent.exe2000.80.2192.0323,58404-Apr-200601:48x86
Sqldiag.exe2000.80.2192.0118,78404-Apr-200604:33x86
Sqldmo.dll2000.80.2192.04,362,24004-Apr-200606:00x86
Sqlevn70.rll2000.80.2192.045,05604-Apr-200606:00Not Applicable
Sqlfth75.dll2000.80.2192.0102,40004-Apr-200602:22x86
Sqlservr.exe2000.80.2192.09,162,75204-Apr-200605:59x86
Sqlsort.dll2000.80.2192.0589,82404-Apr-200606:00x86
Stardds.dll2000.80.2192.0176,12804-Apr-200606:00x86
Svrnetcn.dll2000.80.2192.0110,59204-Apr-200606:00x86
Ums.dll2000.80.2192.035,32804-Apr-200606:00x86
Xpstar.dll2000.80.2192.0311,29604-Apr-200606:00x86
SQL Server 2000, Itanium architecture version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Impprov.dll2000.80.2192.0244,73606-Apr-200611:16IA-64
Msgprox.dll2000.80.2192.0188,41606-Apr-200611:16IA-64
Mssdi98.dll8.11.50523.0758,78406-Apr-200611:16IA-64
Msvcr71.dll7.10.3052.4348,16006-Apr-200611:16x86
Odsole70.dll2000.80.2192.0150,52806-Apr-200611:16IA-64
Osql.exe2000.80.2192.0149,50406-Apr-200611:16IA-64
Pfclnt80.dll2000.80.2192.01,187,84006-Apr-200611:16IA-64
Procsyst.sqlNot Applicable552,06806-Apr-200611:16Not Applicable
Replmerg.exe2000.80.2192.0375,29606-Apr-200611:16IA-64
Replmerg.sqlNot Applicable1,151,45006-Apr-200611:16Not Applicable
Replprov.dll2000.80.2192.0538,62406-Apr-200611:16IA-64
Replprov2.dll2000.80.2192.0538,62406-Apr-200611:16IA-64
Replrec.dll2000.80.2192.0775,16806-Apr-200611:16IA-64
Replrec2.dll2000.80.2192.0775,16806-Apr-200611:16IA-64
Replsub.dll2000.80.2192.0641,02406-Apr-200611:16IA-64
Repltran.sqlNot Applicable1,000,63406-Apr-200611:16Not Applicable
Sqlagent.exe2000.80.2192.01,061,37606-Apr-200611:16IA-64
Sqldiag.exe2000.80.2192.0334,33606-Apr-200611:16IA-64
Sqldmo.dll2000.80.2192.013,860,35206-Apr-200611:16IA-64
Sqlevn70.rll2000.80.2192.035,32806-Apr-200611:16Not Applicable
Sqlfth75.dll2000.80.2192.0246,78406-Apr-200611:16IA-64
Sqlservr.exe2000.80.2192.024,932,86406-Apr-200611:16IA-64
Sqlsort.dll2000.80.2192.0617,47206-Apr-200611:16IA-64
Svrnetcn.dll2000.80.2192.0427,52006-Apr-200611:16IA-64
Xpstar.dll2000.80.2192.0873,47206-Apr-200611:16IA-64

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

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

Steps to reproduce the problem

  1. In SQL Server 2000 SP4, run the following statements by using SQL Query Analyzer.
    use master
    go
    
    create database repro
    go
    
    use repro
    go
    
    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)
    go
    
    create view v1 as
    select t1.* from
    t1 inner join s1 on t1.i = s1.i
    union all
    select t2.* from
    t2 inner join s2 on t2.a = s2.a
    go
    
    create view v2 as
    select t3.* from
    t3 inner join s3 on t3.c = s3.c
    union all
    select t4.* from
    t4 inner join s4 on t4.e = s4.e
    go
    
  2. To make SQL Server return execution information, run the following statements.
    set showplan_text on
    go
  3. Run the following statements, and then examine the output.
    select * from v1 inner join v2 on i = c
    where i = 12 or i = 17
    go
    The following inefficient execution plan is displayed in the output.
    StmtText                                                                                                                
    ----------------------------------------------------------------------------------------------------------------------- 
      |--Concatenation
           |--Nested Loops(Inner Join, WHERE:([t3].[c]=[t1].[i]))
           |    |--Nested Loops(Inner Join)
           |    |    |--Clustered Index Seek(OBJECT:([Repro].[dbo].[s1].[pkt5]), SEEK:([s1].[i]=12) ORDERED FORWARD)
           |    |    |--Clustered Index Seek(OBJECT:([Repro].[dbo].[t1].[pkt1]), SEEK:([t1].[i]=12) ORDERED FORWARD)
           |    |--Nested Loops(Inner Join, OUTER REFERENCES:([t3].[c]))
           |         |--Clustered Index Scan(OBJECT:([Repro].[dbo].[t3].[pkt3]))
           |         |--Clustered Index Seek(OBJECT:([Repro].[dbo].[s3].[pkt7]), SEEK:([s3].[c]=[t3].[c]) ORDERED FORWARD)
           |--Nested Loops(Inner Join, WHERE:([t4].[e]=[t2].[a]))
                |--Nested Loops(Inner Join)
                |    |--Clustered Index Seek(OBJECT:([Repro].[dbo].[s2].[pkt6]), SEEK:([s2].[a]=17) ORDERED FORWARD)
                |    |--Clustered Index Seek(OBJECT:([Repro].[dbo].[t2].[pkt2]), SEEK:([t2].[a]=17) ORDERED FORWARD)
                |--Nested Loops(Inner Join, OUTER REFERENCES:([t4].[e]))
                     |--Clustered Index Scan(OBJECT:([Repro].[dbo].[t4].[pkt4]))
                     |--Clustered Index Seek(OBJECT:([Repro].[dbo].[s4].[pkt8]), SEEK:([s4].[e]=[t4].[e]) ORDERED FORWARD)
    
    (15 row(s) affected)
When you follow these steps in SQL Server 2000 SP3, the following efficient execution plan is displayed in the output.
StmtText                                                                                                                
----------------------------------------------------------------------------------------------------------------------- 
  |--Concatenation
       |--Nested Loops(Inner Join, OUTER REFERENCES:([s3].[c]))
       |    |--Nested Loops(Inner Join, OUTER REFERENCES:([t1].[i]))
       |    |    |--Nested Loops(Inner Join)
       |    |    |    |--Clustered Index Seek(OBJECT:([Repro].[dbo].[s1].[pkt5]), SEEK:([s1].[i]=12) ORDERED FORWARD)
       |    |    |    |--Clustered Index Seek(OBJECT:([Repro].[dbo].[t1].[pkt1]), SEEK:([t1].[i]=12) ORDERED FORWARD)
       |    |    |--Clustered Index Seek(OBJECT:([Repro].[dbo].[s3].[pkt7]), SEEK:([s3].[c]=[t1].[i]) ORDERED FORWARD)
       |    |--Filter(WHERE:(STARTUP EXPR([s3].[c]<13 AND [s3].[c]>7)))
       |         |--Clustered Index Seek(OBJECT:([Repro].[dbo].[t3].[pkt3]), SEEK:([t3].[c]=[s3].[c]) ORDERED FORWARD)
       |--Nested Loops(Inner Join, OUTER REFERENCES:([s4].[e]))
            |--Nested Loops(Inner Join, OUTER REFERENCES:([t2].[a]))
            |    |--Nested Loops(Inner Join)
            |    |    |--Clustered Index Seek(OBJECT:([Repro].[dbo].[s2].[pkt6]), SEEK:([s2].[a]=17) ORDERED FORWARD)
            |    |    |--Clustered Index Seek(OBJECT:([Repro].[dbo].[t2].[pkt2]), SEEK:([t2].[a]=17) ORDERED FORWARD)
            |    |--Clustered Index Seek(OBJECT:([Repro].[dbo].[s4].[pkt8]), SEEK:([s4].[e]=[t2].[a]) ORDERED FORWARD)
            |--Filter(WHERE:(STARTUP EXPR([s4].[e]<24 AND [s4].[e]>19)))
                 |--Clustered Index Seek(OBJECT:([Repro].[dbo].[t4].[pkt4]), SEEK:([t4].[e]=[s4].[e]) ORDERED FORWARD)

(17 row(s) affected)

Properties

Article ID: 917606 - Last Review: October 9, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Personal Edition
Keywords: 
kbautohotfix kbHotfixServer kbqfe KB917606

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com