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
When you synchronize a subscription to a transactional replication publication in Microsoft SQL Server 2000, the synchronization process is slow. During the synchronization process, the CPU usage is high on the computer that is configured as the Distributor.
This problem occurs if the following conditions are true:
- The MSrepl_commands table contains many rows for the publisher database. For example, the MSrepl_commands table contains 800,000 rows for the publisher database.
- The synchronization process initializes the Subscriber or reinitializes the Subscriber. Alternatively, you incrementally add an article to the publication before you synchronize the subscription.
This problem is not specific to transactional replication in SQL Server 2000. This problem may also occur for any query if the following conditions are true:
- You query a table that contains many rows. For example, the table contains 800,000 rows.
- You use the FAST query hint or the TOP query hint in the query.
This problem occurs because SQL Server 2000 generates an inefficient execution plan for one of the queries in the sp_MSget_repl_commands
stored procedure. This problem occurs only if the query that performs poorly uses the FAST query hint or the TOP query hint. The execution plan for the query that performs poorly shows that a join predicate is not pushed down to a Clustered Index Seek
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 now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only 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 SQL Server 2000 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: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.
You must have Microsoft SQL Server 2000 Service Pack 4 (SP4) installed before you 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
You do not have to restart the computer after you apply this hotfix.
You do not have to 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.
Collapse this tableExpand this table
|File name||File version||File size||Date||Time||Platform|
|80sp4-tools.sql||Not Applicable||134,628||18-Feb-2006||09:40||Not Applicable|
|Distmdl.ldf||Not Applicable||786,432||28-Feb-2007||03:17||Not Applicable|
|Distmdl.mdf||Not Applicable||2,359,296||28-Feb-2007||03:17||Not Applicable|
|Instdist.sql||Not Applicable||751,633||28-Nov-2006||23:42||Not Applicable|
|Inst_repl_hotfix.sql||Not Applicable||36||28-Feb-2007||02:03||Not Applicable|
|Procsyst.sql||Not Applicable||552,068||16-Jun-2005||08:15||Not Applicable|
|Replcom.sql||Not Applicable||1,216,659||28-Feb-2007||02:14||Not Applicable|
|Replcom_baseline.sql||Not Applicable||1,214,942||08-Dec-2006||10:08||Not Applicable|
|Replmerg.sql||Not Applicable||1,151,521||28-Feb-2007||05:29||Not Applicable|
|Replmerg_baseline.sql||Not Applicable||1,151,758||28-Feb-2007||02:03||Not Applicable|
|Replsys.sql||Not Applicable||1,096,990||08-Dec-2006||10:03||Not Applicable|
|Replsys_baseline.sql||Not Applicable||1,096,457||08-Dec-2006||10:08||Not Applicable|
|Repltran.sql||Not Applicable||1,000,691||28-Nov-2006||23:42||Not Applicable|
|Repltran_baseline.sql||Not Applicable||999,413||08-Dec-2006||10:08||Not Applicable|
|Sp4_serv_qfe.sql||Not Applicable||18,810||16-Jun-2005||08:15||Not Applicable|
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This hotfix introduces trace flag 9082. You must enable this trace flag to resolve this problem. To enable this trace flag, use the DBCC TRACEON
statement, or specify trace flag 9082 as a startup parameter for SQL Server.
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
Article ID: 929131 - Last Review: June 19, 2007 - Revision: 2.2
- Microsoft SQL Server 2000 Standard Edition
- Microsoft SQL Server 2000, Workgroup Edition
- Microsoft SQL Server 2000 Developer Edition
- Microsoft SQL Server 2000 Enterprise Edition
|kbexpertiseadvanced kbtshoot kbprb KB929131|