Article ID: 931821 - View products that this article applies to.
Bug #: 50000684 (SQL Hotfix)
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.
This article describes the following about this hotfix release:
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.
Cumulative update information for SQL Server 2005 Service Pack 2To 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:
(http://support.microsoft.com/kb/935356/ )Cumulative update package (build 3161) for SQL Server 2005 Service Pack 2 is available
Hotfix information for SQL Server 2005 Service Pack 1A 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:
PrerequisitesYou 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:
(http://support.microsoft.com/kb/913089/ )How to obtain the latest service pack for SQL Server 2005
Restart informationYou do not have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix is not replaced by any other hotfixes.
Registry informationYou do not have to change the registry.
File informationThis 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
Collapse this tableExpand this table
SQL Server 2005 SP1-based hotfix, x64-based version
Collapse this tableExpand this table
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:
822499For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/ )New naming schema for Microsoft SQL Server software update packages
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 931821 - Last Review: October 8, 2011 - Revision: 3.0
Contact us for more help
Connect with Answer Desk for expert help.