Microsoft KB Archive/930484

= FIX: CPU utilization may approach 100 percent on a computer that is running SQL Server 2000 every 49.7 days =

Article ID: 930484

Article Last Modified on 7/5/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition
 * Microsoft SQL Server 2000 Developer Edition
 * Microsoft SQL Server 2000 Enterprise Edition
 * Microsoft SQL Server 2000 Workgroup Edition
 * Microsoft SQL Server 2000 64-bit Edition

-



Bug #: 50000640 (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.



SUMMARY
This article describes the following about this hotfix release:
 * The issues that are fixed by this hotfix package
 * The prerequisites for installing the hotfix package
 * Information about whether you must restart the computer after you install the hotfix package
 * Information about whether you must make any registry changes
 * The files that are contained in the hotfix package



SYMPTOMS
Consider the following scenario. You have a SQL Server 2000 service that is running on a computer that has a system time that is approaching a multiple of 49.7 days from the time when the operating system is restarted. Around this period, you back up a database at least one time, or you restore a database at least one time. In this scenario, CPU utilization may approach 100 percent after the backup operation is complete or after the restore operation is complete. After approximately 15 minutes or less, CPU utilization automatically decreases.

If you back up the database or restore the database when CPU utilization approaches 100 percent, CPU utilization appears to decrease.

Note This problem appears to occur more frequently on Itanium-based computers than on x86-based computers. This problem is very noticeable on the SQL Server servers that perform backup operations or restore operations around this 49.7 day interval.

For a list of all publicly released SQL Server 2000 Post-Service Pack hotfixes, see the following article in the Microsoft Knowledge Base:

894905 Cumulative list of the hotfixes that are available for SQL Server 2000 SP4



CAUSE
This problem continues for approximately 15 minutes. Additionally, this problem occurs every multiple of 49.7 days from the time when the operating system is restarted. This interval is not from the time when the SQL Server service is restarted.

This problem occurs because the SQL worker thread for a backup statement or for a restore statement times out after Windows time wraps around to 0 (zero).

Windows time is the number of milliseconds that have elapsed since the system started. For more information about how to obtain Windows time, visit the following Microsoft Developer Network (MSDN) Web site:

http://msdn2.microsoft.com/en-us/library/ms724408.aspx



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

http://support.microsoft.com/contactus/?ws=support

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.

Prerequisites
 To install the Microsoft SQL Server 2000 Service Pack 3 (SP3) version of this hotfix, you must have SQL Server 2000 SP3 and SQL Server 2000 hotfix build 2000.80.1007 installed.

For more information about how to obtain SQL Server 2000 service packs, 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

For more information about how to obtain SQL Server 2000 hotfix build 2000.80.1007, click the following article number to view the article in the Microsoft Knowledge Base:

893312 FIX: You may receive a &quot;SQL Server could not spawn process_loginread thread&quot; error message, and a memory leak may occur when you cancel a remote query in SQL Server 2000

 To install the Microsoft SQL Server 2000 Service Pack 4 (SP4) version of this hotfix, you must have SQL Server 2000 SP4 installed.

For more information about how to obtain SQL Server 2000 service packs, 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 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 of all the files that you must have to fully update a product to the latest build.

The Japanese 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 Service Pack 4 based hotfix, IA-64 version


STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
To determine whether you are experiencing this problem, make sure that the priority boost option is set to OFF. To configure the priority boost option, use the sp_configure system stored procedure in SQL Server 2000.

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

Keywords: kbexpertiseadvanced kbfix kbhotfixserver kbqfe kbpubtypekc KB930484

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.