Lock:Released Event Class
The Lock:Released event class indicates that a lock on a resource, such as a page, has been released.
The Lock:Acquired and Lock:Released event classes can be used to monitor when objects are being locked, the type of locks taken, and for how long the locks were retained. Locks retained for long periods of time may cause contention issues and should be investigated. For example, an application can be acquiring locks on rows in a table, and then waiting for user input. Because the user input can take a long time to occur, the locks can block other users. In this instance, the application should be redesigned to make lock requests only when needed and not require user input when locks have been acquired.
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 provides the client process ID.
ID of the database in which the lock was released. 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.
Type of event = 23.
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.
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 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.
Resulting mode after the lock was released.
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.
System-assigned ID of the object which was released, if available and applicable.
ID of the related object or entity, if available and applicable.
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, if available.
Text value dependent on the event class captured in the trace.
System-assigned ID of the transaction.