The table title in "SQL event probe" in mssql, such as CPU, Read, Write, Duration, SPID ......

SQL event probe data column
The SQL event probe allows you to select data columns when creating a template. The list of data that you want to return when running the trail. Data displayed in the SQL event probe can be displayed in the event sequence, or by a combination of data columns or data columns.

For example, to identify the user event with the longest execution time, group the event according to DBUserName and Duration. The SQL event probe displays the execution time of each event. This function is similar to the group by clause in Transact-SQL. For more information, see group.



It indicates that you cannot group data by StartTime or EndTime columns.


If the SQL event probe can be connected to the Microsoft®SQL Server™Instance, the Database ID, Object ID, and Index ID columns will be filled with the Database, Object, and Index names respectively. Otherwise, the ID is displayed ).

The following table describes the selected SQL event analyzer data columns by default.

Description of the column number
Application Name1 10 name of the client Application that creates a connection with the SQL Server instance. This column is filled by the value passed by the application, rather than by the displayed program name.
Binary Data 2 is the Binary value associated with the event class captured in the trail.
ClientProcessID1 9 is the ID assigned to the process by the host computer. In this process, the customer application is running. If the client provides the client process ID, this data column is filled.
Column Permissions 44 indicates whether the Column permission is set. Analyze the statement text to determine which permissions are applied to which columns.
Total CPU time used for CPU 18 events (in milliseconds ).
Database ID1 3 USE database statement specifies the database ID. If the USE Database statement is not issued to a given instance, the default database is used. If the Server Name data column is captured in the trail and the Server is available, the SQL event probe displays the database Name. Use the DB_ID function to determine the database value.
The name of the database where the user statement is being run in DatabaseName 35.
DBUserName1 40 the SQL Server user name of the client.
The total Duration (in milliseconds) of the Duration 13 event ).
End Time 15 the Time when the event ends. This column of the event class that starts the event (such as SQL: BatchStarting or SP: Starting) is not filled.
Error 31 indicates the Error number of the event. It is usually the error number stored in sysmessages.
Event class types captured by EventClass1 27.
The type of EventSubClass1 21 event subclass, which provides further information about each event class. For example, the event subclass value of the Execution Warning event class represents the type of the Execution Warning:
1 = query wait. The query can be executed only after resources (such as memory) are executed.
2 = query timeout. The query times out while waiting for the required resources to be executed. This data column of all event classes is not filled.

The logical name of the file modified by FileName 36.
Handle 33 ODBC, ole db, or DB-Library integer used to coordinate server execution.
Host Name1 8 the name of the computer that is running the client. If the client provides a host name, this data column is filled. To determine the host name, use the HOST_NAME function.
Index ID 24 is the Index ID of the object affected by the event. To determine the index ID of an object, use the indid column of the sysindexes system table.
Integer Data 25 is an Integer value related to the event classes captured in the trail.
LoginName 11 user's login name (SQL Server Secure Login or Microsoft Windows®Login creden in the format of DOMAIN \ Username ).
The Security ID (SID) of the LoginSid1 41 logon user ). You can find this information in the sysxlogins table of the master database. The SID is unique for each login on the server.
The integer used to describe the status of events that have been received or are to be requested.
NestLevel 29 indicates the integer of the data returned by @ NESTLEVEL.
Microsoft Windows NT for NT Domain Name1 7 users®4.0 or Windows 2000 domain.
NT User Name1 6 Windows NT 4.0 or Windows 2000 User name.
Object ID 22: the ID of the Object allocated by the system.
ObjectName 34 refers to the object name.
ObjectType 28 indicates the object type value involved in the event. This value corresponds to the type column in sysobjects.
Owner Name 37: Name of the database user of the object Owner.
Permissions 19 indicates the integer value of the checked permission type. Value:
1 = SELECT ALL
2 = UPDATE ALL
4 = REFERENCES ALL
8 = INSERT
16 = DELETE
32 = EXECUTE (process only)
4096 = select any (at least one column)
8192 = UPDATE ANY
16384 = REFERENCES ANY

The Reads 16 server represents the number of Logical Disk Reads performed by the event.
RoleName 38 name of the application role to be enabled.
The name of the SQL Server instance tracked by Server Name1 26.
Severity 20 indicates the Severity of an exception or error.
SPID1 12 the ID of the client-related Server process assigned by SQL Server.
Start Time1 14 time when the event is started (available ).
State 30 is equivalent to the error status code.
Success 23 indicates whether the event is successful. Optional values:
1 = successful.
0 = failed

For example, 1 indicates that the permission check is successful, and 0 indicates that the check fails.

TargetLoginName 42 is the name of the target logon for logon-targeted operations (for example, adding a new logon.
TargetLoginSid 43 is the SID of the target login for Logon operations (for example, adding a new logon.
TargetUserName 39 indicates the name of a database user for operations (for example, granting a user permission.
TextData 1 is the text value associated with the event class captured in the trail. However, if a parameterized query is being tracked, the variable is not displayed with the data value in the TextData column.
Transaction ID 4: The Transaction ID allocated by the system.
The Writes 17 server represents the number of physical disk Writes performed by the event.


1 By default, these data columns are filled for all events.



The filtering definition depends on your tracking purpose. Generally, the following filtering columns are defined:

1. DatabaseName is the same as the name of the database you want to monitor (but this does not seem to work, and the settings on my computer are invalid)
2. DatabaseID is the same as the dbid of the database you want to detect. You can use select db_id (n' name of the database you want to monitor ') to obtain the dbid.
3. ObjectName is the same as the name of the object to be monitored, such as the table name and view name.
4. ObjectID is the same as the id of the object to be monitored. You can use select object_id (n' name of the object to be monitored ') to obtain the id.
5. Error is the same as an Error. If an Error number is often displayed
6. Seccess is the same as 0, failed, 1, and successful. If it is an error, the successful processing will be filtered out.