Microsoft KB Archive/257345

= BUG: SQL Server Books Online States That the Single User Mode Prevents All Locks =

Article ID: 257345

Article Last Modified on 10/16/2003

-

APPLIES TO


 * Microsoft SQL Server 7.0 Standard Edition
 * Microsoft SQL Server 2000 Standard Edition

-



This article was previously published under Q257345



BUG #: 57688 (SQLBUG_70)



SYMPTOMS
The Microsoft SQL Server 7.0 Books Online (BOL) topic "Error 1204" incorrectly states the following:

For a maintenance type of task or for a global update, consider putting the database into single-user mode (if it is feasible to keep other users out of the database). Single-user mode does not set locks, so you will not run out of locks, and the operation will run somewhat faster.

SQL Server does acquire locks for page and extent allocation or deallocation operations, even in single-user mode. This represents a fraction of the locks required for most operations, so it is generally true that in single-user mode you are less likely to run out of locks due to memory constraints and most operations will run somewhat faster. The TRUNCATE TABLE statement is one example of an exception to this because almost all of the locks acquired for a TRUNCATE statement are for extent deallocations.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Keywords: kbbug kbpending KB257345

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.