SQL DEADLOCK TABLE LOCK UPDATE

RangeX_U = Key-Range Conversion lock, created by an overlap of RangeI_N and RangeS_U locks. RangeX_S = Key-Range Conversion lock, created by an overlap of RangeI_N and RangeS_S. RangeI_X = Key-Range Conversion lock, created by an overlap of RangeI_N and X locks. RangeI_U = Key-Range Conversion lock, created by an overlap of RangeI_N and U locks. RangeI_S = Key-Range Conversion lock, created by an overlap of RangeI_N and S locks. RangeI_N (Insert Key-Range and Null Resource lock) = Used to test ranges before inserting a new key into an index.

SQL DEADLOCK TABLE LOCK UPDATE

RangeS_U (Shared Key-Range and Update Resource lock) = Indicates serializable update scan. RangeS_S (Shared Key-Range and Shared Resource lock) = Indicates serializable range scan.

UIX (Update Intent Exclusive) = Indicates an update lock hold on a resource with the intent of acquiring exclusive locks on subordinate resources in the lock hierarchy.

SIX (Shared Intent Exclusive) = Indicates shared access to a resource with the intent of acquiring exclusive locks on subordinate resources in the lock hierarchy. SIU (Shared Intent Update) = Indicates shared access to a resource with the intent of acquiring update locks on subordinate resources in the lock hierarchy. IX (Intent Exclusive) = Indicates the intention to place X locks on some subordinate resource in the lock hierarchy. IU (Intent Update) = Indicates the intention to place U locks on some subordinate resource in the lock hierarchy. IS (Intent Shared) = Indicates the intention to place S locks on some subordinate resource in the lock hierarchy. X (Exclusive) = The holding session is granted exclusive access to the resource. It is used to prevent a common form of deadlock that occurs when multiple sessions lock resources for potential update in the future. U (Update) = Indicates an update lock acquired on resources that may eventually be updated. S (Shared) = The holding session is granted shared access to the resource. Ensures that no other sessions are referencing the indicated object. Sch-M (Schema modification) = Must be held by any session that wants to change the schema of the specified resource. Sch-S (Schema stability) = Ensures that a schema element, such as a table or index, is not dropped while any session holds a schema stability lock on the schema element. NULL = No access is granted to the resource. For granted requests, this is the granted mode for waiting requests, this is the mode being requested.

The value for nonpartitioned lock resources is 0. ID of the lock partition for a partitioned lock resource. This can be an object ID, Hobt ID, or an Allocation Unit ID, depending on the resource type. ID of the entity in a database with which a resource is associated. All resources handled by the lock manager are scoped by the database ID.ĭescription of the resource that contains only information that is not available from other resource columns. ID of the database under which this resource is scoped. Different subtypes do not conflict with each other or with the non-subtyped parent type. Acquiring a subtype lock without holding a non-subtyped lock of the parent type is technically valid. The value can be: DATABASE, FILE, OBJECT, PAGE, KEY, EXTENT, RID, APPLICATION, METADATA, HOBT, ALLOCATION_UNIT, or XACT. This syntax is not supported by serverless SQL pool in Azure Synapse Analytics. To call this from Azure Synapse Analytics or Analytics Platform System (PDW), use the name sys.dm_pdw_nodes_tran_locks.

Sql deadlock table lock