TransactionLog Event Class

 

Applies To: SQL Server 2016

Use the TransactionLog event class to monitor activity in the transaction logs in an instance of the SQL Server Database Engine.

Data column nameData typeDescriptionColumn IDFilterable
ApplicationNamenvarcharName 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.10Yes
BinaryDataimageBinary value dependent on the event class captured in the trace.2Yes
ClientProcessIDintID 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.9Yes
DatabaseIDintID of the database where the data is being logged.3Yes
DatabaseNamenvarcharName of the database in which the user statement is running.35Yes
EventClassintType of event = 54.27No
EventSequenceintSequence of a given event within the request.51No
EventSubClassintType of event subclass.21Yes
GroupIDintID of the workload group where the SQL Trace event fires.66Yes
HostNamenvarcharName 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.8Yes
IndexIDintID for the index on the object affected by the event. To determine the index ID for an object, use the index_id column of the sys.indexes catalog view.24Yes
IntegerDataintInteger value dependent on the event class captured in the trace.25Yes
IsSystemintIndicates whether the event occurred on a system process or a user process. 1 = system, 0 = user.60Yes
LoginNamenvarcharName of the login of the user (either SQL Server security login or the Microsoft Windows login credentials in the form of DOMAIN\username).11Yes
LoginSidimageSecurity identifier (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.41Yes
NTDomainNamenvarcharWindows domain to which the user belongs.7Yes
NTUserNamenvarcharWindows user name.6Yes
ObjectIDintSystem-assigned ID of the object.22Yes
RequestIDintID of the request containing the statement.49Yes
ServerNamenvarcharName of the instance of SQL Server being traced.26No
SessionLoginNamenvarcharLogin 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.64Yes
SPIDintID of the session on which the event occurred.12Yes
StartTimedatetimeTime at which the event started, if available.14Yes
TransactionIDbigintSystem-assigned ID of the transaction.4Yes

sp_trace_setevent (Transact-SQL)
The Transaction Log (SQL Server)

Community Additions

ADD
Show: