BUG: Extraneous Extent Locks Obtained During Data Modification

 Last reviewed: April 29, 1997
Article ID: Q153921
The information in this article applies to:
  • Microsoft SQL Server versions 6.0 and 6.5

SYMPTOMS

Extra Extent locks, located on the next and previous Extents, are being held during data modification statements.

WORKAROUND

There are two possible workarounds to this problem:

  • Increase the configuration option "Locks" to a sufficiently high value.
  • Break down the data modification statements into smaller transactions affecting fewer rows.

MORE INFORMATION

Extent locks are internal locks used by the server for locking Extents. User queries cannot reference or control Extent locking.

For more information, please see the following article in the Microsoft Knowledge Base: 

   Article-ID: Q61795
   Title     : INF: SQL Server Extent Allocation Information.
With data modification statements such as insert, update, and delete, Extent locks are obtained by the server for the purpose of storage structure management. When the transaction results in changes to the Extent structures, locks are also needed on the previous and next Extents to maintain the integrity of the Extent chain. The extra locks were the locks on the next and previous Extents.

This behavior is exhibited noticeably by replication-related tasks, specifically the cleanup task, since cleanup deletes records from distribution database tables and hence can run out of locks on large systems.

Additional query words: extent lock error 1204
Keywords : kbbug6.00 kbbug6.50 SSrvLock
Version : 6.0 6.5
Platform : WINDOWS
Issue type : kbbug
Resolution Type : kbfix

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: April 29, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.