Microsoft KB Archive/818766

= FIX: Intense SQL Server activity results in spinloop wait =

Article ID: 818766

Article Last Modified on 5/16/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Service Pack 3

-



BUG #: 469415 (SQL Server 8.0)



SYMPTOMS
Under extremely rare circumstances, SQL Server can experience a 5-second &quot;batch requests&quot; 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

Hotfix information
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.   Date         Time   Version         Size             File name 26-Feb-2003 03:41  2000.80.777.0      29,244 bytes  Dbmslpcn.dll 25-Apr-2003 02:12                    786,432 bytes  Distmdl.ldf 25-Apr-2003 02:12                  2,359,296 bytes  Distmdl.mdf 30-Jan-2003 01:55                        180 bytes  Drop_repl_hotfix.sql 07-Apr-2003 19:15  2000.80.801.0   1,557,052 bytes  Dtsui.dll 24-Apr-2003 02:51                    747,927 bytes  Instdist.sql 30-Jan-2003 01:55                      1,402 bytes  Inst_repl_hotfix.sql 08-Feb-2003 06:40  2000.80.765.0      90,692 bytes  Msgprox.dll 01-Apr-2003 02:07                      1,873 bytes  Odsole.sql 05-Apr-2003 01:46  2000.80.800.0      62,024 bytes  Odsole70.dll 02-Apr-2003 21:48  2000.80.796.0      57,904 bytes  Osql.exe 02-Apr-2003 23:15  2000.80.797.0     279,104 bytes  Pfutil80.dll 04-Apr-2003 21:27                  1,083,467 bytes  Replmerg.sql 04-Apr-2003 21:53  2000.80.798.0     221,768 bytes  Replprov.dll 08-Feb-2003 06:40  2000.80.765.0     307,784 bytes  Replrec.dll 01-Apr-2003 02:23                  1,084,828 bytes  Replsys.sql 16-Apr-2003 22:39                    115,892 bytes  Sp3_serv_uni.sql 07-Apr-2003 17:44                     25,172 bytes  Sqldumper.exe 19-Mar-2003 18:20  2000.80.789.0      28,672 bytes  Sqlevn70.rll 24-Apr-2003 05:39  2000.80.811.0     176,696 bytes  Sqlmap70.dll 08-Feb-2003 06:40  2000.80.765.0      57,920 bytes  Sqlrepss.dll 30-Apr-2003 23:52  2000.80.816.0   7,540,817 bytes  Sqlservr.exe 08-Feb-2003 06:40  2000.80.765.0      45,644 bytes  Sqlvdi.dll 26-Feb-2003 03:41  2000.80.777.0      29,244 bytes  Ssmslpcn.dll 26-Feb-2003 03:41  2000.80.777.0      82,492 bytes  Ssnetlib.dll 30-Apr-2003 23:52  2000.80.816.0      45,132 bytes  Ums.dll 28-Feb-2003 01:34  2000.80.778.0      98,872 bytes  Xpweb70.dll 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.



STATUS
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.



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:

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.

