FIX: Intense SQL Server Activity Results in Spinloop Wait in SQL Server 2000 Service Pack 2

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.
   Date         Time   Version            Size    File name   --------------------------------------------------------------   24-Jan-2003  18:53  2000.80.732.0      29,244  Dbmslpcn.dll        18-Jan-2003  02:23                    786,432  Distmdl.ldf   18-Jan-2003  02:23                  2,359,296  Distmdl.mdf   11-Dec-2002  17:50                        180  Drop_repl_hotfix.sql   02-Jul-2002  15:35  2000.80.650.0     107,088  Impprov.dll         17-Jan-2003  20:33                    774,409  Instdist.sql   11-Dec-2002  17:50                      1,402  Inst_repl_hotfix.sql   20-Aug-2002  16:24  2000.80.679.0     111,172  Logread.exe         15-Dec-2002  23:21  2000.80.717.0      90,692  Msgprox.dll         05-Mar-2003  18:17  2000.80.736.0      62,024  Odsole70.dll        03-Jan-2002  01:59                     18,185  Qfe356326.sql   20-Aug-2002  16:47  2000.80.679.0     135,748  Qrdrsvc.exe         26-Aug-2002  22:49  2000.80.679.0     406,088  Rdistcom.dll        04-Oct-2001  01:36                    437,302  Replcom.sql   20-Aug-2002  16:33  2000.80.679.0     152,136  Replmerg.exe        25-Nov-2002  21:43                  1,004,990  Replmerg.sql   15-Dec-2002  23:21  2000.80.717.0     221,768  Replprov.dll        15-Dec-2002  23:21  2000.80.717.0     303,688  Replrec.dll         22-Jan-2003  19:27                  1,002,101  Replsys.sql   04-Oct-2001  01:36                    881,228  Repltran.sql   26-Aug-2002  22:49  2000.80.679.0     283,208  Rinitcom.dll        16-Sep-2002  22:31                    390,045  Securityhotfix.sql   26-Aug-2002  22:49  2000.80.679.0      28,672  Sqlagent.dll        26-Aug-2002  18:39  2000.80.679.0     311,872  Sqlagent.exe        28-Aug-2002  16:32  2000.80.679.0      49,152  Sqlagent.rll   26-Aug-2002  22:49  2000.80.679.0      53,824  Sqlcmdss.dll        28-Aug-2002  16:40  2000.80.679.0      12,288  Sqlcmdss.rll   14-Jan-2003  21:39  2000.80.725.0     172,600  Sqlmap70.dll        02-May-2003  18:44  2000.80.743.0   7,483,473  Sqlservr.exe        01-Nov-2002  18:56  2000.80.698.0      45,644  Sqlvdi.dll          24-Jan-2003  18:53  2000.80.732.0      29,244  Ssmslpcn.dll        24-Jan-2003  18:53  2000.80.732.0      82,492  Ssnetlib.dll        02-Jan-2003  20:12  2000.80.722.0      25,148  Ssnmpn70.dll        02-May-2003  18:44  2000.80.743.0      49,228  Ums.dll             07-Apr-2002  02:08  2000.80.606.0      70,208  Xplog70.dll         07-Apr-2002  02:08  2000.80.606.0      53,828  Xpqueue.dll         07-Apr-2002  02:08  2000.80.606.0     156,228  Xprepl.dll          12-Jul-2002  01:00  2000.80.658.0     279,104  Xpstar.dll          16-Sep-2002  23:12  2000.80.686.0      98,872  Xpweb70.dll
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.
More information
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

Article ID: 818763 - Last Review: 10/26/2013 07:58:00 - Revision: 3.0

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbfix kbbug KB818763