BUG: Table Creation Deadlocks in Tempdb Leave Stray Tables

 Last reviewed: May 2, 1997
Article ID: Q151304

The information in this article applies to:
  • Microsoft SQL Server, version 6.0
BUG#: 11342

SYMPTOMS

When a client repeatedly runs a stored procedure that creates tables in tempdb, and deadlocks are encountered on the tempdb system tables, the temp tables will not always be cleaned up when the stored procedure terminates (nor when the client disconnects).

This happens only on multiprocessor computers, but was replicated with SQL Server version 4.21a SP4 as well as 6.0 on Alpha, MIPS, and Intel computers. The problem also happens with both Windows NT 3.5 and 3.51, but was not replicated on any uniprocessor computer.

WORKAROUND

To avoid deadlock, trace flag 1204 should be used to detect and analyze the cause of deadlock condition.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: deadlock
Keywords : kbbug6.00 kbprg SSrvLock
Version : 6.0
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.