PRB: Extraneous Extent Locks Obtained During Data Modification (153921)


The information in this article applies to:

  • Microsoft SQL Server 6.0
  • Microsoft SQL Server 6.5
This article was previously published under Q153921

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:

61795 : 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.

Modification Type:MinorLast Reviewed:3/16/2005
Keywords:kbBug kbfix kbprb KB153921
©2004 Microsoft Corporation. All rights reserved.