FIX: Client Disconnects Can Cause SQL Server Instability When Using More Than Two Gigabytes of Memory

ID: Q248483

The information in this article applies to:

Microsoft SQL Server version 6.5

BUG #: 18923 (SQLBUG_65)

SYMPTOMS

When a client disconnects from SQL Server, the connection can persist. The sp_who stored procedure can show the offending process as having a status of SPINLOOP. In this state, the process is impossible to KILL and can continue to hold locks indefinitely. In addition, the process can cause an access violation (AV). Another symptom is that SQL Server can stop responding (hang).

CAUSE

This problem is caused due to a hashing algorithm SQL Server uses to manage memory. When SQL server is configured to use memory above 2 GB, this can hash to a value greater than was accounted for. This caused an internal overflow and so the process was not cleaned up properly.

RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next SQL Server service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

The English version of this fix should have the following file attributes or later:


   Date        Time     Version      Size      File name    Platform
   -----------------------------------------------------------------

   11/18/99   12:50p   6.50.466   4,538,007   SQL466A.EXE   Alpha
   11/18/99   12:44p   6.50.466   2,719,017   SQL466I.EXE   Intel

NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files may also contain additional files.

WORKAROUND

To work around this problem, make sure that SQL Server is configured to only use 2 gigabytes or less of memory.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.5.

Additional query words: GB

Keywords : SSrvGen kbbug6.50
Version : winnt:6.5
Platform : winnt
Issue type : kbbug