--- title: "Lock:Escalation Event Class | Microsoft Docs" ms.custom: "" ms.date: "03/14/2017" ms.prod: sql ms.reviewer: "" ms.technology: supportability ms.topic: conceptual helpviewer_keywords: - "Escalation event class" - "lock escalation [SQL Server], event class" ms.assetid: d253b44c-7600-4afa-a3a7-03cc937c6a4b author: "stevestein" ms.author: "sstein" monikerRange: "=azuresqldb-current||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current" --- # Lock:Escalation Event Class [!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)] The **Lock:Escalation** event class indicates that a finer-grained lock has been converted to a coarser-grained lock; for example, a row lock that is converted to an object lock. The escalation event class is Event ID 60. ## Lock:Escalation Event Class Data Columns |Data column name|Data type|Description|Column ID|Filterable| |----------------------|---------------|-----------------|---------------|----------------| |**ApplicationName**|**nvarchar**|Name of the client application that created the connection to an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. This column is populated with the values passed by the application rather than the displayed name of the program.|10|Yes| |**ClientProcessID**|**int**|ID assigned by the host computer to the process where the client application is running. This data column is populated if the client provides the client process ID.|9|Yes| |**DatabaseID**|**int**|ID of the database in which the lock was acquired. [!INCLUDE[ssSqlProfiler](../../includes/sssqlprofiler-md.md)] displays the name of the database if the **ServerName** data column is captured in the trace and the server is available. Determine the value for a database by using the DB_ID function.|3|Yes| |**DatabaseName**|**nvarchar**|Name of the database in which the escalation occurred.|35|Yes| |**EventClass**|**int**|Type of event = 60.|27|No| |**EventSubClass**|**int**|Cause of the lock escalation:

**0 - LOCK_THRESHOLD** indicates the statement exceeded the lock threshold.

**1 - MEMORY_THRESHOLD** indicates the statement exceeded the memory threshold.|21|Yes| |**EventSequence**|**int**|Sequence of a given event within the request.|51|No| |**GroupID**|**int**|ID of the workload group where the SQL Trace event fires.|66|Yes| |**HostName**|**nvarchar**|Name of the computer on which the client is running. This data column is populated if the client provides the host name. To determine the host name, use the HOST_NAME function.|8|Yes| |**IntegerData**|**int**|HoBT lock count. The number of locks for the HoBT at the time of lock escalation.|25|Yes| |**IntegerData2**|**int**|Escalated lock count. The total number of locks that were converted. These lock structures are deallocated because they are already covered by the escalated lock.|55|Yes| |**IsSystem**|**int**|Indicates whether the event occurred on a system process or a user process. 1 = system, 0 = user.|60|Yes| |**LineNumber**|**int**|Line number of [!INCLUDE[tsql](../../includes/tsql-md.md)] statement.|5|Yes| |**LoginName**|**nvarchar**|Name of the login of the user (either [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] security login or the [!INCLUDE[msCoName](../../includes/msconame-md.md)] Windows login credentials in the form of DOMAIN\username).|11|Yes| |**LoginSid**|**image**|Security identification number (SID) of the logged-in user. You can find this information in the **sys.server_principals** catalog view. Each SID is unique for each login in the server.|41|Yes| |**Mode**|**int**|Resulting lock mode after the escalation:

0=NULL - Compatible with all other lock modes (LCK_M_NL)

1=Schema Stability lock (LCK_M_SCH_S)

2=Schema Modification Lock (LCK_M_SCH_M)

3=Shared Lock (LCK_M_S)

4=Update Lock (LCK_M_U)

5=Exclusive Lock (LCK_M_X)

6=Intent Shared Lock (LCK_M_IS)

7=Intent Update Lock (LCK_M_IU)

8=Intent Exclusive Lock (LCK_M_IX)

9=Shared with intent to Update (LCK_M_SIU)

10=Shared with Intent Exclusive (LCK_M_SIX)

11=Update with Intent Exclusive (LCK_M_UIX)

12=Bulk Update Lock (LCK_M_BU)

13=Key range Shared/Shared (LCK_M_RS_S)

14=Key range Shared/Update (LCK_M_RS_U)

15=Key Range Insert NULL (LCK_M_RI_NL)

16=Key Range Insert Shared (LCK_M_RI_S)

17=Key Range Insert Update (LCK_M_RI_U)

18=Key Range Insert Exclusive (LCK_M_RI_X)

19=Key Range Exclusive Shared (LCK_M_RX_S)

20=Key Range Exclusive Update (LCK_M_RX_U)

21=Key Range Exclusive Exclusive (LCK_M_RX_X)|32|Yes| |**NTDomainName**|**nvarchar**|Windows domain to which the user belongs.|7|Yes| |**NTUserName**|**nvarchar**|Windows user name.|6|Yes| |**ObjectID**|**int**|System-assigned ID of the table for which lock escalation was triggered.|22|Yes| |**ObjectID2**|**bigint**|ID of the related object or entity. (HoBT ID for which the lock escalation was triggered.)|56|Yes| |**Offset**|**int**|Starting offset of [!INCLUDE[tsql](../../includes/tsql-md.md)] statement.|61|Yes| |**OwnerID**|**int**|1=TRANSACTION

2=CURSOR

3=SESSION

4=SHARED_TRANSACTION_WORKSPACE

5=EXCLUSIVE_TRANSACTION_WORKSPACE

6=WAITFOR_QUERY|58|Yes| |**RequestID**|**int**|ID of the request containing the statement.|49|Yes| |**ServerName**|**nvarchar**|Name of the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] being traced.|26|No| |**SessionLoginName**|**nvarchar**|Login name of the user who originated the session. For example, if you connect to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] using Login1 and execute a statement as Login2, **SessionLoginName** shows Login1 and **LoginName** shows Login2. This column displays both [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] and Windows logins.|64|Yes| |**SPID**|**int**|ID of the session on which the event occurred.|12|Yes| |**StartTime**|**datetime**|Time at which the event started, if available.|14|Yes| |**TextData**|**ntext**|Text of the [!INCLUDE[tsql](../../includes/tsql-md.md)] statement that caused lock escalation.|1|Yes| |**TransactionID**|**bigint**|System-assigned ID of the transaction.|4|Yes| |**Type**|**int**|Lock escalation granularity:

1=NULL_RESOURCE

2=DATABASE

3=FILE

5=OBJECT (table level)

6=PAGE

7=KEY

8=EXTENT

9=RID

10=APPLICATION

11=METADATA

12=HOBT

13=ALLOCATION_UNIT|57|Yes| ## Examples The following example uses the `sp_trace_create` procedure to create a trace, uses `sp_trace_setevent` to add lock escalation columns to the trace, and then uses `sp_trace_setstatus` to start the trace. In statements such as `EXEC sp_trace_setevent @TraceID, 60, 22, 1`, the number `60` indicates the escalation event class, `22` indicates the **ObjectID** column, and `1` sets the trace event to ON. ``` DECLARE @RC int, @TraceID int; EXEC @rc = sp_trace_create @TraceID output, 0, N'C:\TraceResults'; -- Set the events and data columns you need to capture. EXEC sp_trace_setevent @TraceID, 60, 1, 1; -- 1 = TextData EXEC sp_trace_setevent @TraceID, 60, 12, 1; -- 12 = SPID EXEC sp_trace_setevent @TraceID, 60, 21, 1; -- 21 = EventSubClass EXEC sp_trace_setevent @TraceID, 60, 22, 1; -- 22 = ObjectID EXEC sp_trace_setevent @TraceID, 60, 25, 1; -- 25 = IntegerData EXEC sp_trace_setevent @TraceID, 60, 55, 1; -- 25 = IntegerData2 EXEC sp_trace_setevent @TraceID, 60, 57, 1; -- 57 = Type -- Set any filter by using sp_trace_setfilter. -- Start the trace. EXEC sp_trace_setstatus @TraceID, 1; GO ``` Now that the trace is running, execute the statements that you want to trace. When they finish, execute the following code to stop and then close the trace. This example uses the `fn_trace_getinfo` function to get the `traceid` to be used in the `sp_trace_setstatus` statements. ``` -- After the trace is complete. DECLARE @TraceID int; -- Find the traceid of the current trace. SELECT @TraceID = traceid FROM ::fn_trace_getinfo(default) WHERE value = N'C:\TraceResults.trc'; -- First stop the trace. EXEC sp_trace_setstatus @TraceID, 0; -- Close and then delete its definition from SQL Server. EXEC sp_trace_setstatus @TraceID, 2; GO ``` ## See Also [sp_trace_setevent (Transact-SQL)](../../relational-databases/system-stored-procedures/sp-trace-setevent-transact-sql.md) [sys.dm_tran_locks (Transact-SQL)](../../relational-databases/system-dynamic-management-views/sys-dm-tran-locks-transact-sql.md)