---
title: "SP:StmtCompleted Event Class | Microsoft Docs"
ms.custom: ""
ms.date: "06/13/2017"
ms.prod: "sql-server-2014"
ms.reviewer: ""
ms.technology: supportability
ms.topic: conceptual
topic_type: 
  - "apiref"
helpviewer_keywords: 
  - "SP:StmtCompleted event class"
ms.assetid: 9e8147a4-aeeb-49a6-80f8-df753d0f34cc
author: stevestein
ms.author: sstein
manager: craigg
---
# SP:StmtCompleted Event Class
  The SP:StmtCompleted event class indicates that a [!INCLUDE[tsql](../../includes/tsql-md.md)] statement within a stored procedure has completed.  
  
## SP:StmtCompleted Event Class Data Columns  
  
|Data column name|`Data type`|Description|Column ID|Filterable|  
|----------------------|-------------------|-----------------|---------------|----------------|  
|ApplicationName|`nvarchar`|Name of the client application that created the connection to an instance of [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. This column is populated with the values passed by the application rather than the displayed name of the program.|10|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|  
|CPU|`int`|Amount of CPU time (in milliseconds) used by the event.|18|Yes|  
|DatabaseID|`int`|ID of the database in which the stored procedure is running. Determine the value for a database by using the DB_ID function.|3|Yes|  
|DatabaseName|`nvarchar`|Name of the database in which the stored procedure is running.|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 = 45.|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|  
|IntegerData|`int`|Integer value dependent on the event class captured in the trace.|25|Yes|  
|IntegerData2|`int`|End offset (in bytes) of the statement that is being executed.|55|Yes|  
|IsSystem|`int`|Indicates whether the event occurred on a system process or a user process. 1 = system, 0 = user.|60|Yes|  
|LineNumber|`int`|Line number of the statement being executed.|5|Yes|  
|LoginName|`nvarchar`|Name of the login of the user (either [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] security login or the [!INCLUDE[msCoName](../../includes/msconame-md.md)] 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|  
|NestLevel|`int`|Integer representing the data returned by @@NESTLEVEL.|29|Yes|  
|NTDomainName|`nvarchar`|Windows domain to which the user belongs.|7|Yes|  
|NTUserName|`nvarchar`|Windows user name.|6|Yes|  
|ObjectID|`int`|System-assigned ID of the object.|22|Yes|  
|ObjectName|`nvarchar`|Name of the object being referenced.|34|Yes|  
|ObjectType|`int`|Value 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](objecttype-trace-event-column.md).|28|Yes|  
|Offset|`int`|Starting offset of the statement within the stored procedure or batch.|61|Yes|  
|Reads|`bigint`|Number of logical disk reads performed by the server on behalf of the event.|16|Yes|  
|RequestID|`int`|ID of the request containing the statement.|49|Yes|  
|RowCounts|`bigint`|The number of rows affected by an event.|48|Yes|  
|ServerName|`nvarchar`|Name of the instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] being traced.|26|No|  
|SessionLoginName|`nvarchar`|Login name of the user who originated the session. For example, if you connect to [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] using Login1 and execute a statement as Login2, SessionLoginName shows Login1 and LoginName shows Login2. This column displays both [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] and Windows logins.|64|Yes|  
|SourceDatabaseID|`int`|The ID of the database the object exists in.|62|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|  
|Writes|`bigint`|Number of physical disk writes performed by the server on behalf of the event.|17|Yes|  
|XactSequence|`bigint`|Token that describes the current transaction.|50|Yes|  
  
## See Also  
 [Extended Events](../extended-events/extended-events.md)   
 [sp_trace_setevent (Transact-SQL)](/sql/relational-databases/system-stored-procedures/sp-trace-setevent-transact-sql)