<_locDefinition> <_locDefault _loc="locNone" /> <_locTag _loc="locData">DESCRIPTION <_locTag _loc="locData">BESTPRACTICE Command Events Collection of events for commands. Discover Events Collection of events for discover requests. Discover Server State Events Collection of events for server state discovers. Errors and Warnings Collection of events for server errors. Notification Events Collection of notification events. Progress Reports Collection of events for progress reporting. Queries Events Collection of events for queries. Query Processing Collection of events for a query execution. Security Audit Collection of database audit event classes. Session Events Collection of session events. 1 Collects all new connection events since the trace was started, such as when a client requests a connection to a server running an instance of SQL Server. 2 Collects all new disconnect events since the trace was started, such as when a client issues a disconnect command. 4 Records service shut down, start, and pause activities. 5 Progress report begin. 6 Progress report end. 7 Progress report current. 8 Progress report error. 9 Query begin. 10 Query end. 11 Query subcube, for Usage Based Optimization. 12 Query subcube with detailed information. This event may have a negative impact on performance when turned on. 15 Command begin. 16 Command end. 17 Server error. 18 Records object permission changes. 19 Records server backup/restore. 33 Start of Server State Discover. 34 Contents of the Server State Discover Response. 35 End of Server State Discover. 36 Start of Discover Request. 38 End of Discover Request. 39 Notification event. 40 Existing user connection. 41 Query subcube with detailed information. This event may have a negative impact on performance when turned on. 42 Existing session. 43 Session Initialize. 60 Answer query by getting data from aggregation. This event may have a negative impact on performance when turned on. 61 Answer query by getting data from one of the caches. This event may have a negative impact on performance when turned on. 70 Query cube Begin. 71 Query cube End. 72 Calculate Non Empty Begin. 73 Calculate Non Empty Current. 74 Calculate Non Empty End. 75 Serialize results Begin. 76 Serialize Results Current. 77 Serialize Results End. 78 Execute MDX Script Begin. 79 Execute MDX Script Current. 80 Execute MDX Script End. 81 Query Dimension. 0 Event Class is used to categorize events. 1 Event Subclass provides additional information about each event class. 2 Time at which the event started, when available. For filtering, expected formats are 'YYYY-MM-DD' and 'YYYY-MM-DD HH:MM:SS'. 3 Time at which the event started, when available. For filtering, expected formats are 'YYYY-MM-DD' and 'YYYY-MM-DD HH:MM:SS'. 4 Time at which the event ended. This column is not populated for starting event classes, such as SQL:BatchStarting or SP:Starting. For filtering, expected formats are 'YYYY-MM-DD' and 'YYYY-MM-DD HH:MM:SS'. 5 Amount of time (in milliseconds) taken by the event. 6 Amount of CPU time (in milliseconds) used by the event. 7 Job ID for progress. 8 Session type (what entity caused the operation). 9 Progress total. 10 Integer data. 11 Object ID (note this is a string). 12 Object type. 13 Object name. 14 Object path. A comma-separated list of parents, starting with the object's parent. 15 Object reference. Encoded as XML for all parents, using tags to describe the object. 22 Severity level of an exception. 23 1 = success. 0 = failure (for example, a 1 means success of a permissions check and a 0 means a failure of that check). 24 Error number of a given event. 25 Unique connection ID. 28 Name of the database in which the statement of the user is running. 32 Windows user name. 33 Windows domain to which the user belongs. 35 Name of the computer on which the client is running. This data column is populated if the host name is provided by the client. 36 The process ID of the client application. 37 Name of the client application that created the connection to the server. This column is populated with the values passed by the application rather than the displayed name of the program. 39 Session GUID. 40 User name in canonical form. For example, engineering.microsoft.com/software/someone. 41 Server process ID. This uniquely identifies a user session. This directly corresponds to the session GUID used by XML/A. 42 Text data associated with the event. 43 Name of the server producing the event. 44 Parameters for parameterized queries and commands. 45 XMLA request properties. 46 Binary value dependent on the event class captured in the trace.