Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: High CPU utilization by SQL Server 2005 may occur when you use NUMA architecture on a computer that has SQL Server 2005 installed


View products that this article applies to.

Bug #: 50000684 (SQL Hotfix)

↑ Back to the top


Microsoft distributes Microsoft SQL Server 2005 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 2005 fix release.

↑ Back to the top


Summary

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

↑ Back to the top


Symptoms

Consider the following scenario. You have Microsoft SQL Server 2005 installed on a computer. You use non-uniform memory access (NUMA) architecture on the computer. In this scenario, SQL Server 2005 may represent a large percentage of the utilization of one or more CPUs. This may be true even when no queries are running.

This high CPU utilization may be likely to occur soon after the SQL Server service starts. The high CPU utilization occurs on the lazy writer thread. When you query the sysprocesses system table, you see that one or more rows of the table have a value of LAZY WRITER in the cmd column. If you query this table repeatedly while this problem occurs, you may notice that the value of the cpu column for one or more of these rows constantly increases.

↑ Back to the top


Resolution

Cumulative update information for SQL Server 2005 Service Pack 2

To resolve this problem, install the cumulative update package (build 3161) for SQL Server 2005 Service Pack 2. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

935356 Cumulative update package (build 3161) for SQL Server 2005 Service Pack 2 is available

Hotfix information for SQL Server 2005 Service Pack 1

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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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 SQL Server 2005 Service Pack 1 (SP1) installed. For more information about how to obtain SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

913089 How to obtain the latest service pack for SQL Server 2005

Restart information

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.

Registry information

You do not have to change the registry.

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 2005 SP1-based hotfix, x86-based version
File nameFile versionFile sizeDateTimePlatform
Databasemailengine.dll9.0.2216.075,12025-Jan-200720:39x86
Logread.exe2005.90.2216.0400,75225-Jan-200720:40x86
Microsoft.analysisservices.adomdclient.dll9.0.2216.0546,16025-Jan-200720:40x86
Microsoft.analysisservices.deploymentengine.dll9.0.2216.0140,65625-Jan-200720:40x86
Microsoft.analysisservices.dll9.0.2216.01,217,90425-Jan-200720:40x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2216.078,19225-Jan-200720:40x86
Microsoft.sqlserver.sqlenum.dll9.0.2216.0910,70425-Jan-200720:40x86
Msasxpress.dll9.0.2216.024,94425-Jan-200720:40x86
Msgprox.dll2005.90.2216.0200,56025-Jan-200720:40x86
Msmdlocal.dll9.0.2216.015,645,55225-Jan-200720:40x86
Msmdredir.dll9.0.2216.03,993,96825-Jan-200720:40x86
Mssqlsystemresource.ldfNot Applicable524,28825-Jan-200718:03Not Applicable
Mssqlsystemresource.mdfNot Applicable40,108,03225-Jan-200718:03Not Applicable
Qrdrsvc.exe2005.90.2216.0369,52025-Jan-200720:40x86
Rdistcom.dll2005.90.2216.0643,44025-Jan-200720:40x86
Repldp.dll2005.90.2216.0187,24825-Jan-200720:40x86
Replmerg.exe2005.90.2216.0320,88025-Jan-200720:40x86
Replprov.dll2005.90.2216.0550,25625-Jan-200720:40x86
Replrec.dll2005.90.2216.0784,75225-Jan-200720:40x86
Replsub.dll2005.90.2216.0407,40825-Jan-200720:40x86
Spresolv.dll2005.90.2216.0177,00825-Jan-200720:40x86
Sqlaccess.dll2005.90.2216.0350,57625-Jan-200720:40x86
Sqlagent90.exe2005.90.2216.0321,39225-Jan-200720:40x86
Sqlservr.exe2005.90.2216.028,972,45625-Jan-200720:40x86
Sysdbupg.sqlNot Applicable218,48625-Jan-200713:53Not Applicable
Xmlsub.dll2005.90.2216.0195,44025-Jan-200720:41x86
Xpstar90.dll2005.90.2216.0295,28025-Jan-200720:41x86
Xpstar90.rll2005.90.2216.0155,50425-Jan-200720:40x86
SQL Server 2005 SP1-based hotfix, x64-based version
File nameFile versionFile sizeDateTimePlatform
Databasemailengine.dll9.0.2216.075,12025-Jan-200700:28x86
Logread.exe2005.90.2216.0525,16825-Jan-200700:28x64
Microsoft.analysisservices.adomdclient.dll9.0.2216.0546,16022-Jan-200720:40x86
Microsoft.analysisservices.adomdclient.dll9.0.2216.0546,16025-Jan-200700:28x86
Microsoft.analysisservices.deploymentengine.dll9.0.2216.0140,65622-Jan-200720:40x86
Microsoft.analysisservices.dll9.0.2216.01,217,90422-Jan-200720:40x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2216.078,19222-Jan-200720:40x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2216.094,06425-Jan-200700:28x64
Microsoft.sqlserver.sqlenum.dll9.0.2216.0877,93625-Jan-200700:28x86
Msasxpress.dll9.0.2216.024,94422-Jan-200720:40x86
Msasxpress.dll9.0.2216.030,06425-Jan-200700:28x64
Msgprox.dll2005.90.2216.0262,00025-Jan-200700:28x64
Msmdlocal.dll9.0.2216.015,645,55222-Jan-200720:40x86
Msmdredir.dll9.0.2216.03,993,96822-Jan-200720:40x86
Mssqlsystemresource.ldfNot applicable524,28822-Jan-200718:03Not applicable
Mssqlsystemresource.mdfNot applicable40,108,03222-Jan-200718:03Not applicable
Qrdrsvc.exe2005.90.2216.0434,03225-Jan-200700:28x64
Rdistcom.dll2005.90.2216.0836,46425-Jan-200700:28x64
Repldp.dll2005.90.2216.0187,24822-Jan-200720:40x86
Repldp.dll2005.90.2216.0237,93625-Jan-200700:28x64
Replmerg.exe2005.90.2216.0417,64825-Jan-200700:28x64
Replprov.dll2005.90.2216.0747,88825-Jan-200700:28x64
Replrec.dll2005.90.2216.01,011,05625-Jan-200700:28x64
Replsub.dll2005.90.2216.0528,24025-Jan-200700:28x64
Spresolv.dll2005.90.2216.0225,64825-Jan-200700:28x64
Sqlaccess.dll2005.90.2216.0357,74425-Jan-200700:28x86
Sqlagent90.exe2005.90.2216.0392,56025-Jan-200700:28x64
Sqlservr.exe2005.90.2216.039,365,48825-Jan-200700:28x64
Sysdbupg.sqlNot applicable218,48629-Dec-200613:53Not applicable
Xmlsub.dll2005.90.2216.0319,85625-Jan-200700:28x64
Xpstar90.dll2005.90.2216.0543,60025-Jan-200700:28x64
Xpstar90.rll2005.90.2216.0156,01625-Jan-200700:28x64

↑ Back to the top


Status

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

↑ Back to the top


More Information

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:

822499 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:

824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top


Keywords: kb, kbautohotfix, kbsql2005engine, kbexpertiseadvanced, kbfix, kbhotfixserver, kbqfe, kbpubtypekc

↑ Back to the top

Article Info
Article ID : 931821
Revision : 1
Created on : 1/7/2017
Published on : 10/8/2011
Exists online : False
Views : 513