<_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. File Load and Save Collection of events for file load and save operations reporting. Job Graph Events Collection of events related to database processing job dependencies Locks Collection of lock related events. M Data Provider Events Collection of events collected from the M Data Provider 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 key events during the process of a query execution. Resource Governance Collection of events for resource governance. 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/synchronize/attach/detach/imageload/imagesave. 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 User defined Event. 41 Existing user connection. 42 Existing session. 43 Session Initialize. 50 Metadata locks deadlock. 51 Metadata lock timeout. 52 The locks were acquired by the transaction 53 The locks were released by the transaction 54 The locks are held by another transaction and therefore this transaction is blocking until the locks are released 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. Deprecated. 80 Execute MDX script end. 81 Query dimension. 82 VertiPaq SE Query 83 VertiPaq SE Query 84 Reports reads, writes, cpu usage after end of commands and queries. 85 VertiPaq SE Query Cache Use 86 VertiPaq SE Query Cache Miss 90 File Load Begin. 91 File Load End. 92 File Save Begin. 93 File Save End 94 PageOut Begin. 95 PageOut End 96 PageIn Begin. 97 PageIn End 98 DirectQuery Begin. 99 DirectQuery End. 110 Information about the evaluation of calculations. This event will have a negative impact on performance when turned on. 111 Detailed information about the evaluation of calculations. This event will have a negative impact on performance when turned on. 112 DAX logical/physical plan tree for VertiPaq and DirectQuery modes. 113 Workload Group is throttled on CPU usage 114 Workload group exceeds the memory limit 115 Workload group exceeds the processing limit 120 DAX extension function execution begin event. 121 DAX extension function execution end event. 122 DAX extension function error trace event directly traced by extension authors. 123 DAX extension function informational/telemetry trace event directly traced by extension authors. 124 DAX extension function verbose trace event directly traced by extension authors. 126 An error occurred during MDX script execution. 130 Collection of all queries that are executed against the data source 131 A query was rewritten according to available aggregate tables. 132 Information about aggregation table matching. 133 Information about DAX query shape. 134 Job graph related events 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 The activity ID is used to track the request(s) from the same operation. 47 The request ID is used to track a request. 48 Expression being evaluated when error occurred. 49 Error Type: 0 = unknown, 1 = user, 2 = system. 50 Name of the Dax extension function being executed. 51 User Object ID. 52 The value of the ApplicationContext XMLA property as provided by external applications to assist with end-to-end correlation of user activities. 54 User defined name of the database in which the statement of the user is running. 55 Identity information of current user 56 ProfilerAdded column