SP:StmtCompleted Event Class


The SP:StmtCompleted event class indicates that a Transact-SQL statement within a stored procedure has completed.

Data column nameData typeDescriptionColumn IDFilterable
ApplicationNamenvarcharName of the client application that created the connection to an instance of Microsoft SQL Server. This column is populated with the values passed by the application rather than the displayed name of the program.10Yes
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 ID.9Yes
CPUintAmount of CPU time (in milliseconds) used by the event.18Yes
DatabaseIDintID of the database in which the stored procedure is running. Determine the value for a database by using the DB_ID function.3Yes
DatabaseNamenvarcharName of the database in which the stored procedure is running.35Yes
DurationbigintAmount of time (in microseconds) taken by the event.13Yes
EndTimedatetimeTime at which the event ended. This column is not populated for starting event classes, such as SQL:BatchStarting or SP:Starting.15Yes
EventClassintType of event = 45.27No
EventSequenceintSequence of a given event within the request.51No
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
IntegerDataintInteger value dependent on the event class captured in the trace.25Yes
IntegerData2intEnd offset (in bytes) of the statement that is being executed.55Yes
IsSystemintIndicates whether the event occurred on a system process or a user process. 1 = system, 0 = user.60Yes
LineNumberintLine number of the statement being executed.5Yes
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 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.41Yes
NestLevelintInteger representing the data returned by @@NESTLEVEL.29Yes
NTDomainNamenvarcharWindows domain to which the user belongs.7Yes
NTUserNamenvarcharWindows user name.6Yes
ObjectIDintSystem-assigned ID of the object.22Yes
ObjectNamenvarcharName of the object being referenced.34Yes
ObjectTypeintValue representing the type of the object involved in the event. This value corresponds to the type column in the sys.objects catalog view. For values, see ObjectType Trace Event Column.28Yes
OffsetintStarting offset of the statement within the stored procedure or batch.61Yes
ReadsbigintNumber of logical disk reads performed by the server on behalf of the event.16Yes
RequestIDintID of the request containing the statement.49Yes
RowCountsbigintThe number of rows affected by an event.48Yes
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
SourceDatabaseIDintThe ID of the database the object exists in.62Yes
SPIDintID of the session on which the event occurred.12Yes
StartTimedatetimeTime at which the event started, if available.14Yes
TextDatantextText value dependent on the event class captured in the trace.1Yes
TransactionIDbigintSystem-assigned ID of the transaction.4Yes
WritesbigintNumber of physical disk writes performed by the server on behalf of the event.17Yes
XactSequencebigintToken that describes the current transaction.50Yes

Extended Events
sp_trace_setevent (Transact-SQL)