Lock:Deadlock Event Class
The Lock:Deadlock event class is produced when an attempt to acquire a lock is canceled because the attempt was part of a deadlock and was chosen as the deadlock victim.
Use the Lock:Deadlock event class to monitor when deadlocks occur and which objects are involved. You can use this information to determine if deadlocks are significantly affecting the performance of your application. You can then examine the application code to determine if you can make changes to minimize deadlocks.
Data column name
Name of the client application that created the connection to an instance of SQL Server. This column is populated with the values passed by the application rather than the displayed name of the program.
Lock resource identifier.
ID assigned by the host computer to the process where the client application is running. This data column is populated if the client process ID is provided by the client.
ID of the database in which the lock was being acquired. SQL Server Profiler 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.
Name of the database in which the lock was being acquired.
Amount of time (in microseconds) between the time the lock request was issued and the time the deadlock occurred.
Time at which the deadlock ended.
Type of event = 25.
The sequence of a given event within the request.
ID of the workload group where the SQL Trace event fires.
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.
Deadlock number. Numbers are assigned beginning with 0 when the server is started and are incremented for each deadlock.
Identified for informational purposes only. Not supported. Future compatibility is not guaranteed.
Indicates whether the event occurred on a system process or a user process. 1 = system, 0 = user.
Name of the login of the user (either SQL Server security login or the Microsoft Windows login credentials in the form of DOMAIN\username).
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.
The resulting mode after the deadlock.
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)
Windows domain to which the user belongs.
Windows user name.
ID of the object in contention, if available and applicable.
ID of the related object or entity, if available and applicable.
The ID of the request containing the statement.
Name of the instance of SQL Server being traced.
Login name of the user who originated the session. For example, if you connect to SQL Server using Login1 and execute a statement as Login2, SessionLoginName shows Login1 and LoginName shows Login2. This column displays both SQL Server and Windows logins.
ID of the session on which the event occurred.
Time at which the event started, when available.
Text value dependent on the lock type that was being acquired.
System-assigned ID of the transaction.