Lock:Timeout (timeout > 0) Event Class
The Lock:Timeout (timeout > 0) event class indicates that a request for a lock on a resource, such as a page, has timed out because another transaction is holding a blocking lock on the required resource. This event class behaves the same as the Lock:Timeout event class, except it does not include any events where the timeout value is 0.
Include the Lock:Timeout (timeout > 0) event class in traces where you are using lock probes or other processes that have timeout values of zero. This allows you to see where actual time-outs are occurring without seeing time-out values of zero.
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 timeout occurred. 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 time-out occurred.
Amount of time (in microseconds) taken by the event.
Time at which the event ended. This column is not populated for starting event classes, such as SQL:BatchStarting or SP:Starting.
Type of event=189.
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 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.
State that the event has received or is requesting.
Windows domain to which the user belongs.
Windows user name.
ID of the object, 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.