MSSQL error: 17883, severity: 1, status: 0

The company uses an old SQL Server 100% database, and the CPU usage lasts for several times (once or multiple times) for in a week, causing no response from the application, as shown in: the error message is as follows: date 20137122: 14: 03 log SQLServer (archive No. 6

The company has an old SQL SERVER 2000 database, and the CPU usage lasts for several times (once or multiple times) for 100% in a week, causing no response from the application, as shown in: the error message is as follows: log SQL Server (archive number 6-2:14:03) Source server Message error: 17883, strict

The company has an old SQL SERVER 2000 database, and the CPU usage lasts for several times (once or multiple times) for 100% in a week, causing no response from the application, as shown in:

The error message is as follows:

Date: 2:14:03 log SQL Server (archive No. 6-8:49:00) Source server Message error: 17883, severity: 1, Server space, status: 0 on 2:14:03 log SQL Server (archive number 6-8:49:00) Source server Message scheduler 2 seems to have been suspended. SPID 18, ECID 0, UMS context 0x03A1B5D0.

View Code

The database versions and patches are as follows:

Code Snippet

View the official Microsoft documentation and prompt the cause of error: the Checkpoint Process forces SQL Server to write all dirty pages to the disk. Supporting and maintaining a fast I/O rate and a system that does not cause an I/O attempt to be suspended can trigger a situation where the checkpoint process does not need to be delayed to wait for the completion of the I/O process. When the checkpoint is not correctly generated, it will affect the entire database activity and performance. This may reduce the transaction volume and the batch commit rate. The following error message may appear in the SQL Server Error Log:

Error: 17883, severity: 1, status: 0
The scheduler 0 seems to have been suspended. SPID 7, ECID 0, UMS context 0x045530B8.

Solution:

From the official Microsoft documentation, This is a bug in SQL SERVER 2000 and requires patches. The specific references are as follows:

Service Pack information

To solve this problem, obtain the latest Microsoft SQL Server 2000 Service Pack. For other information, 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

Security Patch Information

This fix is provided along with the security patch for the Microsoft Security Bulletin MS03-031. For more information about how to obtain this security patch from the Microsoft download center, click the following article number to view the article in the Microsoft Knowledge Base:

815495 ()

MS03-031: SQL Server Cumulative Security Patches

821277 ()

MS03-031: security patches for SQL Server 2000 Service Pack 3

Bytes ----------------------------------------------------------------------------------------------------------------------

This problem has not occurred in the last few days since patching. You need to observe it for a while to see if such problems still occur, to determine whether the patch actually solves this problem.

References:

? Id = 18384

, Hong Kong server