Export (0) Print
Expand All

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

Data type

Description

Column ID

Filterable

ApplicationName

nvarchar

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.

10

Yes

BinaryData

image

Lock resource identifier.

2

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 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.

3

Yes

DatabaseName

nvarchar

Name of the database in which the time-out occurred.

35

Yes

Duration

bigint

Amount of time (in microseconds) taken by the event.

13

Yes

EndTime

datetime

Time at which the event ended. This column is not populated for starting event classes, such as SQL:BatchStarting or SP:Starting.

15

Yes

EventClass

int

Type of event=189.

27

No

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

IntegerData2

int

Identified for informational purposes only. Not supported. Future compatibility is not guaranteed.

55

Yes

IsSystem

int

Indicates whether the event occurred on a system process or a user process. 1 = system, 0 = user.

60

Yes

LoginName

nvarchar

Name of the login of the user (either SQL Server security login or the Microsoft 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

State that the event has received or is requesting.

0=NULL

1=Sch-S

2=Sch-M

3=S

4=U

5=X

6=IS

7=IU

8=IX

9=SIU

10=SIX

11=UIX

12=BU

13=RangeS-S

14=RangeS-U

15=RangeI-N

16=RangeI-S

17=RangeI-U

18=RangeI-X

19=RangeX-S

20=RangeX-U

21=RangeX-X

32

Yes

NTDomainName

nvarchar

Windows domain to which the user belongs.

7

Yes

NTUserName

nvarchar

Windows user name.

6

Yes

ObjectID

int

ID of the object, if available and applicable.

22

Yes

ObjectID2

bigint

ID of the related object or entity, if available and applicable.

56

Yes

OwnerID

int

1=TRANSACTION

2=CURSOR

3=SESSION

4=SHARED_TRANSACTION_WORKSPACE

5=EXCLUSIVE_TRANSACTION_WORKSPACE

58

Yes

RequestID

int

ID of the request containing the statement.

49

Yes

ServerName

nvarchar

Name of the instance of SQL Server being traced.

26

No

SessionLoginName

nvarchar

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.

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 value dependent on the event class captured in the trace.

1

Yes

TransactionID

bigint

System-assigned ID of the transaction.

4

Yes

Type

int

1=NULL_RESOURCE

2=DATABASE

3=FILE

5=OBJECT

6=PAGE

7=KEY

8=EXTENT

9=RID

10=APPLICATION

11=METADATA

12=AUTONAMEDB

13=HOBT

14=ALLOCATION_UNIT

57

Yes

Community Additions

ADD
Show:
© 2014 Microsoft