This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 469416 (SQL Server 8.0)
In extremely rare situations, SQL Server may experience a 5-second "batch requests" stall condition. This condition is frequently described as delayed or stalled batch event processing for a 5-second period and is accompanied by a spike in SQL Server connections during or immediately following the stall pattern.
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.
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, submit a request to 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. The English version of this fix has the file attributes (or later) 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 these files may also contain additional files.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
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:
When the spin count is exceeded, the penalty can result in a delay of up to a 5,000 milliseconds, and the status of the server process ID in the sysprocesses table changes to spinloop. A status of spinloop indicates that you may be experiencing this problem. This hotfix reduces the delay to a maximum of 1 millisecond.
Note It is highly unusual to experience this problem on a single processor computer. For additional information about this problem in SQL Server 2000 SP3, click the following article number to view the article in the Microsoft Knowledge Base:
818766 FIX: Intense SQL Server Activity Results in Spinloop Wait