This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 469415 (SQL Server 8.0)
Under extremely rare circumstances, SQL Server can experience a 5-second "batch requests" stall condition. This is frequently described as delayed or stalled batch event processing for a 5-second period that is accompanied by a spike in SQL Server connections during or immediately following the stall pattern.
Service pack information
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional 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
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 tool in Control Panel.
Note Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files. Note This hotfix does not apply to SQL Server 2000 64-bit.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.
SQL Server 2000 uses spin count synchronization primitives to provide appropriate internal synchronization and access to internal structures.
For more information about spinning synchronization, visit the following Microsoft Web site:
InitializeCriticalSectionAndSpinCount When the spin count is exceeded, the penalty can result in up to a 5,000-millisecond delay and the status of the server process ID in the sysprocesses table changes to spinloop. A status equal to spinloop indicates that you may be experiencing the problem. This correction reduces the delay to a maximum of 1 millisecond.
Note It is highly unusual to see this situation on a single processor computer.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
818763 FIX: Intense SQL Server Activity Results in Spinloop Wait in SQL Server 2000 Service Pack 2