SP:StmtStarting Event Class
Applies to: 
SQL Server
Azure SQL Database
Azure SQL Managed Instance
The SP:StmtStarting event class indicates that a Transact-SQL statement within a stored procedure has started.
SP:StmtStarting 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 SQL Server. 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 |
| 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 |
| EventClass | int | Type of event = 44. | 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 | 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 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 |
| 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. | 28 | Yes |
| Offset | int | Starting offset of the statement within the stored procedure or batch. | 61 | 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 |
| SourceDatabaseID | int | 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 |
| State | int | Indicates if the execution of the statement is occurring after a recompile. 1=Recompiled |
30 | 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 |
| XactSequence | bigint | Token used to describe the current transaction. | 50 | Yes |