<_locDefinition> <_locDefault _loc="locNone" /> <_locTag _loc="locData">DESCRIPTION <_locTag _loc="locData">BESTPRACTICE Broker Includes event classes that are produced by Service Broker. CLR Includes event classes that are produced by execution of .Net Common Language Runtime (CLR) objects inside SQL Server. Cursors Includes event classes that are produced by cursor operations. Database Includes event classes that are produced when data or log files grow or shrink automatically. Deprecation Includes deprecation related events. Errors and Warnings Includes event classes that are produced when a SQL Server error or warning is returned; for example, an error during the compilation of a stored procedure or an exception in SQL Server. Full text Includes event classes that are produced when full-text searches are started, interrupted, or stopped. Locks Includes event classes that are produced when a lock is acquired, cancelled, released, or has some other action performed on it. Objects Includes event classes that are produced when database objects are created, dropped, or altered. OLEDB Includes event classes that are produced by OLE DB calls. Performance Includes event classes that are produced when SQL data manipulation (DML) operators execute. Progress Report Includes the Progress Report: Online Index Operation event class. Query Notifications Includes event classes produced by query notifications processing. Scans Includes event classes that are produced when tables and indexes are scanned. Security Audit Includes event classes that are used to audit server activity. Server Includes general server events. Sessions Includes server session event classes. Stored Procedures Includes event classes produced by the execution of stored procedures. Transactions Includes event classes produced by the execution of Microsoft Distributed Transaction Coordinator transactions or by writing to the transaction log. TSQL Includes event classes produced by the execution of Transact-SQL statements passed to an instance of SQL Server from the client. User configurable Includes event classes that you can define. 10 Occurs when a remote procedure call has been completed. 11 Occurs when a remote procedure call has started. 12 Occurs when the Transact-SQL statement has completed. 13 Occurs when a Transact-SQL batch is starting. 14 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. 15 Collects all new disconnect events since the trace was started, such as when a client issues a disconnect command. 16 Collects all attention events, such as client interrupt request or when a client connection is broken. 17 Indicates properties of existing user connections when trace was started. Server fires one ExistingConnection event per user connection. 18 Records service shut down, start, and pause activities. 19 Tracks MS DTC coordinated transactions between two or more databases. 20 Indicates that a login attempt to SQL Server from a client failed. 21 Indicates events logged in the Windows application event log. 22 Indicates error events logged in the SQL Server error log. 23 Indicates that a lock on a resource, such as a data page, has been released.\r\nThe Lock:Acquired and Lock:Released event classes can be used to monitor when objects are being locked, the type of locks taken, and for how long the locks were retained. Locks retained for long periods of time may cause contention issues and should be investigated. 24 Indicates that acquisition of a lock on a resource, such as a data page, has been achieved.\r\nThe Lock:Acquired and Lock:Released event classes can be used to monitor when objects are being locked, the type of locks taken, and for how long the locks were retained. Locks retained for long periods of time may cause contention issues and should be investigated. 25 Indicates that two concurrent transactions have deadlocked each other by trying to obtain incompatible locks on resources that the other transaction owns. 26 Indicates that the acquisition of a lock on a resource has been canceled (for example, due to a deadlock). 27 Indicates that a request for a lock on a resource, such as a page, has timed out due to another transaction holding a blocking lock on the required resource. 28 Describes the degree of parallelism assigned to the SQL statement. 33 Indicates that an exception has occurred in SQL Server. 34 Indicates when a stored procedure is not found in the procedure cache. 35 Indicates when an item is inserted into the procedure cache. 36 Indicates when an item is removed from the procedure cache. 37 Indicates that the stored procedure is recompiling. 38 Indicates when a procedure is found in the cache. 39 Indicates the context of the local state for the executing procedure. 40 Occurs when the Transact-SQL statement is starting. 41 Occurs when the Transact-SQL statement has completed. 42 Indicates when the stored procedure has started. 43 Indicates when the stored procedure has completed. 44 Indicates that a Transact-SQL statement within a stored procedure has started. 45 Indicates that a Transact-SQL statement within a stored procedure has completed. 46 Indicates when an object has been created, such as for CREATE INDEX, CREATE TABLE, and CREATE DATABASE statements. 47 Indicates when an object has been deleted, such as in DROP INDEX and DROP TABLE statements. 50 Tracks BEGIN TRANSACTION, COMMIT TRANSACTION, SAVE TRANSACTION, and ROLLBACK TRANSACTION statements. 51 Indicates when a table or index scan has started. 52 Indicates when a table or index scan has stopped. 53 Indicates when a cursor has been opened on an Transact-SQL statement. 54 Tracks when transaction are written to the transaction log. 55 Occurs when a hash recursion, or cessation of hashing (hash bail) has occurred during a hashing operation. 58 Collects the events associated with the automatic creation and updating of statistics. 59 Is produced for each of the events leading up to the deadlock. 60 A finer-grained lock has been converted to a coarser-grained lock. 61 Indicates that an OLE DB error has occurred. 67 Indicates any warnings that occurred during the execution of a SQL Server statement or stored procedure. 68 Displays the plan tree of the SQL statement being executed. The Showplan Text (Unencoded) event class is the same as the Showplan Text event class, except the event information is formatted as text rather than as binary data. 69 Indicates sort operations that do not fit into memory. Does not include sort operations involving the creation of indexes, only sort operations within a query (such as an ORDER BY clause used in a SELECT statement). 70 Occurs when the Microsoft SQL Server 2005 Database Engine compiles a SELECT statement associated with a cursor into an execution plan but does not create the cursor. 71 Indicates when an SQL statement or statements have been prepared for use by ODBC, OLE DB or DB-Library. 72 Indicates when a prepared Transact-SQL statement or statements have been executed by SqlClient, ODBC, OLE DB or DB-Library. 73 Indicates that the SqlClient, ODBC, OLE DB, or DB-Library has unprepared (deleted) a prepared Transact-SQL statement or statements. 74 Occurs when Microsoft SQL Server 2005 Database Engine creates and populates a cursor from the execution plan created by a cursor prepare event. 75 Occurs when the Microsoft SQL Server 2005 Database Engine recompiles a Transact-SQL cursor due to a schema change. 76 Occurs when the Microsoft SQL Server 2005 Database Engine executes a Transact-SQL statement that is not supported by server cursors of the type requested. SQL Server database engine returns an error that indicates the cursor type has changed. 77 Occurs when the Microsoft SQL Server 2005 Database Engine discards an execution plan. 78 Occurs when the Microsoft SQL Server 2005 Database Engine closes and deallocates a cursor. 79 Indicates that column statistics which would have been useful to the query optimizer are not present. This can cause the optimizer to choose a less efficient query plan than otherwise expected. You will not see this event produced unless the option to auto-create statistics is turned off. 80 Indicates that a predicate joining two tables is not present. This can potentially result in long-running queries or inaccurate results. This event is only produced if both sides of the join return more than one row. 81 Indicates when SQL Server memory usage increases or decreases by 1 megabyte or 5% of the maximum server memory, whichever is greater. 82 Used to monitor user-defined events that cannot be monitored by the system-supplied events in other event categories. 83 Used to monitor user-defined events that cannot be monitored by the system-supplied events in other event categories.. 84 CUsed to monitor user-defined events that cannot be monitored by the system-supplied events in other event categories. 85 Used to monitor user-defined events that cannot be monitored by the system-supplied events in other event categories. 86 Used to monitor user-defined events that cannot be monitored by the system-supplied events in other event categories. 87 Used to monitor user-defined events that cannot be monitored by the system-supplied events in other event categories. 88 Used to monitor user-defined events that cannot be monitored by the system-supplied events in other event categories. 89 Used to monitor user-defined events that cannot be monitored by the system-supplied events in other event categories. 90 Used to monitor user-defined events that cannot be monitored by the system-supplied events in other event categories. 91 Used to monitor user-defined events that cannot be monitored by the system-supplied events in other event categories. 92 Indicates that the data file grew automatically. This event does not get triggered if the data file is grown explicitly through ALTER DATABASE. 93 Indicates that the log file grows automatically. This event does not get triggered if the log file is grown explicitly through ALTER DATABASE. 94 Indicates that the data file has been shrunk. 95 Indicates that the log file has been shrunk. 96 Displays the query-plan tree of the SQL statement being executed. Include the Showplan Text event class to identify the Showplan operators on SQL Server 2000 or SQL Server 7.0. This event class will also work on SQL Server 2005, however the information included is a subset of the information available in Showplan All, Showplan XML Statistics Profile or Showplan XML. 97 Displays the query-plan with full compile-time details (including costing estimates and column lists) of the SQL statement being executed. When the Showplan All event class is included in a trace, the BinaryData data column must be selected. If it is not, information for this event class will not be displayed in the trace. 98 Displays the query-plan with full run-time details (including actual number of rows passing through each operation) of the SQL statement, which was executed. When the Showplan Statistics Profile event class is included in a trace, the BinaryData data column must be selected. If it is not, information for this event class will not be displayed in the trace. 100 Information about output parameters of previously executed remote procedure call. 102 Records GRANT, DENY, REVOKE statement permission events. 103 Records GRANT, DENY, REVOKE object permission events. 104 Records add and drop actions on SQL Server logins for sp_addlogin and sp_droplogin. 105 Records grant, revoke, and deny actions on Windows account login rights for sp_grantlogin, sp_revokelogin, and sp_denylogin. 106 Records modifications on login property, except passwords, for sp_defaultdb and sp_default language. 107 Records SQL Server login password changes. Passwords are not recorded. 108 Records addition or removal of logins to a fixed server role for sp_addsrvrolemember and sp_dropsrvrolemember. 109 Records addition and removal of database users (Windows or SQL Server). 110 Records addition and removal of members to a database role (fixed or user-defined) for sp_addrolemember, sp_droprolemember, and sp_changegroup. 111 Records add or drop actions on database roles for sp_addrole and sp_droprole. 112 Records changes on the password of an application. 113 Records use of statement permissions. 114 Records use of object permissions, successfully or unsuccessfully. 115 Records BACKUP and RESTORE events. 116 Records DBCC commands issued. 117 Records AUDIT modifications. 118 Records when a CREATE, ALTER, or DROP command is issued for the specified object. 119 Displays OLE DB provider calls made by SQL Server for distributed queries and remote stored procedures. 120 Displays OLE DB IUnknown::QueryInterface calls made by SQL Server for distributed queries and remote stored procedures. 121 Displays OLE DB IRowset::GetData calls made by SQL Server for fetching row data for distributed queries and remote stored procedures. 122 Occurs when SQL Server executes a SQL Statement. Include the Showplan XML event class to identify the Showplan operators. The event class stores each event as a well defined XML document. 123 Displays performance information about individual Full-Text queries, including the query itself, the number of rows returned, and the duration of the query. 124 Reports the progress of a Service Broker conversation. 125 Occurs when you use a feature that will be removed from future version of SQL Server, but will not be removed from the next major release of SQL Server. For greatest longevity of your applications, you should avoid using features that cause the Deprecation Announcement event class or the Deprecation Final Support event class. 126 Occurs when you use a feature that will be removed from the next major release of SQL Server. For greatest longevity of your applications, avoid using features that cause the Deprecation Announcement event class or the Deprecation Final Support event class. 127 The Exchange Spill event class indicates that communication buffers in a parallel query plan have been temporarily written to the tempdb database. This occurs rarely and only when a query plan has multiple range scans. 128 Occurs when a database is created, altered, or dropped. 129 Occurs when a CREATE, ALTER or DROP statement is executed on database objects, such as schemas. 130 Occurs when principals, such as users, are created, altered, or dropped from a database. 131 Occurs when a CREATE, ALTER or DROP statement is executed on schema objects, such as tables or views. 132 Occurs when there is an impersonation in server scope, such as execute as login. 133 Occurs when an impersonation occurs within the database scope, such as execute as user or setuser. 134 Occurs when the owner is changed for objects in server scope. 135 Occurs when the owner is changedfor objects in database scope, such as assembly. 136 Occurs when Service Broker creates a new conversation group or drops an existing conversation group. 137 Indicates that a task has been blocked for more than a specified amount of time. This event class does not include system tasks or tasks which are waiting on non deadlock-detectable resources. To configure the frequency of reporting, use the sp_configure command to configure the blocked process threshold option. 138 Reports the status of a transport connection managed by Service Broker. 139 Occurs when Service Broker forwards a message. 140 Occurs when Service Broker drops a message that was intended to be forwarded. 141 Occurs when Service Broker determines the routing for a message. A message is classified for either local, remote, or delayed delivery. 142 Indicates that errors have occurred in the Service Broker Transport layer. The error number and state values indicate the source of the error. 143 Indicates a poison message was detected because there were five transaction rollbacks in a row on a Service Broker queue. The event contains the database ID and Queue ID of the queue that contains the poison message. 144 Occurs when the state of an active mirrored route (i.e. a route containing a mirror address that is currently being used by at least one conversation that is transmitting messages) changes. This reflects the change of state of one of the connections used by the mirrored route. This event also contains the status of those connections (eg. connected as primary, connected as mirror, disconnected due to some transport problem). 146 Occurs when SQL Server executes a SQL Statement. Include the Showplan XML Statististics Profile event class to identify the Showplan operators on SQL Server 2005. 148 Occurs simultaneously with the Lock:Deadlock event class. The Deadlock Graph event class provides an XML description of the deadlock. 149 Indicates when an Acknowledgement has been received. 150 Indicates that a trace file has been closed during rollback. 152 Occurs when the permissions to change the owner of a database is checked. This happens when the ALTER AUTHORIZATION statement is used to change the owner of a database. 153 Occurs when the permissions to change the owner of schema object (such as a table, procedure, or function) is checked. This happens when the ALTER AUTHORIZATION statement is used to assign an owner to an object. 155 Indicates that a full-text crawl (population) has started. Use this event class to check if a crawl request is actually being picked up by worker tasks. 156 Indicates that a full-text crawl (population) has stopped. The stop could due to a successfully completed crawl or a fatal error. 157 Indicates that an exception has been encountered during a full-text crawl. The error will usually cause the full-text crawl to stop. Check the Windows event log or the crawl log for more detailed error information. 158 Records both successful and unsuccessful Conversations. 159 Records both successful and unsuccessful adjacent Broker logins. 160 Occurs when Service Broker is unable to retain a received message that should have been delivered to a service in this instance. For messages that should have been forwarded, see Broker:Forwarded Message Dropped Event Class. 161 Occurs when Service Broker receives a corrupted message. 162 Displays the error message as seen by the user in the case or an error or exception. The error message text appears in the TextData field. 163 Occurs when a queue monitor starts an activation stored procedure, sends a QUEUE_ACTIVATION notification, or when an activation stored procedure started by a queue monitor exits. 164 Indicates an object has been altered (for example, by ALTER INDEX, ALTER TABLE, or ALTER DATABASE statements). Each DDL operation fires 2 complete events: 1 for "Begin" phase and another for either "Commit" or "Rollback" phase. 165 Indicates that a compiled plan has been cached for the first time, recompiled, or evicted from the plan cache. 166 Occurs when a statement in a batch (including stored procedures) recompiles. This event should be used in SQL Server 2005 instead of SP:Recompile to trace statement-level recompilations. 167 Indicates when the state of a mirrored database changes. 168 Occurs when SQL Server compiles a SQL Statement. Include the Showplan XML For Query Compile event class to identify the Showplan operators on SQL Server 2005. 169 Occurs when SQL Server compiles a SQL Statement. Include the Showplan All for Query Compile event class to identify the Showplan operators on SQL Server 2000 or SQL Server 7.0. This event class will also work on SQL Server 2005, however the information included is a subset of the information available in Showplan XML For Query Compile. 170 Occurs in the case of a GDR event for permissions in server scope, such as create login. 171 Occurs when a GDR event for a schema object, such as table or function, occurs. 172 Occurs when a GDR event for database objects such as assemblies and schemas, occurs. 173 Occurs when Audit operations in server, such as alter setting, resources, external access, or authorization are used. 175 Occurs for all statements that check for the ALTER TRACE permission. Statements that check for ALTER TRACE include those used to create or configure a trace, or to set a filter on trace. 176 Occurs in the case of CREATE, ALTER or DROP for server objects. 177 Occurs in the case of create, alter or drop for server principals. 178 Occurs when various operations in a database, such as checkpoint or subscribe query notification, occur. 180 Occurs when database objects, such as schemas, are accessed. 181 Indicates that a BEGIN TRANSACTION request is starting. The request was sent from the client through Transaction Management interface. 182 Indicates that a BEGIN TRANSACTION request has been completed. The request was sent from the client through Transaction Management interface. 183 Indicates that a PROMOTE TRANSACTION request is starting. The request was sent from the client through Transaction Management interface. 184 Indicates that a PROMOTE TRANSACTION request has completed. The request was sent from the client through Transaction Management interface. 185 Indicates that a COMMIT TRANSACTION request is starting. The request was sent from the client through Transaction Management interface. 186 Indicates that a COMMIT TRANSACTION request completed. The request was sent from the client through Transaction Management interface. 187 Indicates that a ROLLBACK TRANSACTION request is starting. The request was sent from the client through Transaction Management interface. 188 Indicates that a ROLLBACK TRANSACTION request completed. The request was sent from the client through Transaction Management interface. 189 Indicates that a request for a lock on a resource, such as a page, has timed out due to another transaction holding a blocking lock on the required resource. This event class behaves the same as the Lock:Timeout event class, except it does not include any events where the timeout value is 0. 190 Indicates the progress of an online index build operation. In most situations, the online index build process is a long running operation. This event class can be used to view the progress of an online index build while it is running. 191 Indicates that a SAVE TRANSACTION request is starting. The request was sent from the client through Transaction Management interface. 192 Indicates that a SAVE TRANSACTION request has completed. The request was sent from the client through Transaction Management interface. 193 Occurs when a background job has terminated abnormally. This condition may require the attention of a system administrator. 194 Occurs when a distributed query is run and collects information corresponding to the provider connection. This event class contains all the properties collected from the remote provider using various property sets such as DBPROPSET_DATASOURCEINFO, SQLPROPSET_OPTHINTS, DBPROPSET_SQLSERVERDATASOURCEINFO (SQL Server only), DBPROPSET_SQLSERVERDBINIT (SQL Server only) and DBPROPSET_ROWSET and interface IDBInfo. 195 Occurs when a tape mount request is received. Use this event class any time you want to monitor tape mount requests and their success or failure. 196 Occurs when a request to load an assembly is executed. This can be useful when troubleshooting a query that uses CLR, when troubleshooting a slow running server that is running CLR queries, or when monitoring a server to gather user, database, success, or other information about assembly loads. 198 Occurs when SQL Server 2005 executes an XQuery. This event class provides the static type of the XQuery expression. In case of the value() method, the statically inferred type is displayed after the implied atomization of the expression. 199 Identifies activities related to ongoing subscription registration and subscription firing. 200 Allows to track creation and deletion of internal parameter tables. Those tables are used to store information about active subscriptions. 201 Allows to track when a new subscription request falls into an already existing class of (Match) or a new class (Create). The third event subclass (Drop) stands for cleanup of templates for query classes without active subscriptions. 202 Tracks internal activities of query notifications. 1 Text value dependent on the event class captured in the trace. 2 Binary value dependent on the event class captured in the trace. 3 ID of the database specified by the USE database statement, or the default database if no USE database statement has been issued for a given connection. 4 System-assigned ID of the transaction. 5 Displays the number of the line containing the error. 6 Windows user name. 7 Windows domain to which the user belongs. 8 Name of the computer on which the client is running. This data column is populated if the host name is provided by the client. To determine the host name, use the HOST_NAME function. 9 The process ID of the application calling SQL Server. 10 Name of the client application that created the connection to SQL Server. This column is populated with the values passed by the application rather than the displayed name of the program. 11 Name of the login of the user (either SQL Server security login or the Windows login credentials in the form of DOMAIN\Username). 12 Server Process ID assigned by SQL Server to the process associated with the client. 13 Amount of time taken by the event. Although the server measures duration in microseconds, SQL Server Profiler can display the value in milliseconds, depending on the setting in the Tools>Options dialog. 14 Time at which the event started, when available. 15 Time at which the event ended. This column is not populated for starting event classes, such as SQL:BatchStarting or SP:Starting. 16 Number of logical disk reads performed by the server on behalf of the event. 17 Number of physical disk writes performed by the server on behalf of the event. 18 Amount of CPU time (in milliseconds) used by the event. 19 Integer value representing the type of permissions checked. 20 Severity level of an exception. 21 Type of event subclass. This data column is not populated for all event classes. 22 System-assigned ID of the object. 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 ID for the index on the object affected by the event. To determine the index ID for an object, use the indid column of the sysindexes system table. 25 Integer value dependent on the event class captured in the trace. 26 Name of the SQL Server traced. 27 Event class name. 28 Value representing the type of the object involved in the event. This value corresponds to the type column in sysobjects. 29 Integer representing the data returned by @@NESTLEVEL. 30 Equivalent to an error state code. 31 Error number of a given event. Often this is the error number stored in sysmessages. 32 Integer used by various events to describe a state the event has received or is requesting. 33 Integer used by ODBC, OLE DB, or DB-Library to coordinate execution with the server. 34 The name of the object being referenced. 35 Name of the database in which the statement of the user is running. 36 The logical name of the file being modified. 37 Database user name of the object owner. 38 Name of an application role being enabled. 39 For actions which target a database user (for instance, granting permission to a user), the name of that user. 40 SQL Server user name of the client. 41 Security identification number (SID) of the logged-in user. You can find this information in the syslogins table of the master database. Each SID is unique for each login in the server. 42 For actions which target a login (for instance, adding a new login), the name of the targeted login. 43 For actions which target a login (for instance, adding a new login), the security identification number (SID) of the targeted login. 44 Indicator of whether a column permission was set. Parse the statement text to determine exactly which permissions were applied to which columns. 45 Name of the linked server. 46 Name of the OLE DB provider. 47 Name of the OLE DB method. 48 The number of rows in the batch. 49 The ID of the request containing the statement. 50 A token to describe the current transaction. 51 The sequence of a given event within the request. 52 Bigint value dependent on the event class captured in the trace. 53 Bigint value dependent on the event class captured in the trace. 54 GUID value dependent on the event class captured in the trace. 55 Integer value dependent on the event class captured in the trace. 56 The ID of the related object or entity if available. 57 Integer value dependent on the event class captured in the trace. 58 Type of the object owning a lock (for lock events) 59 The name of the schema the object is within. 60 Indicates whether the event occurred on a system process or a user process. 1 = system, 0 = user. 61 The starting offset of the statement within the stored procedure or batch. 62 ID of the Database in which the source of the object exists. 63 64 bit hash based on the text of an adhoc query or the database and object ID of a sql object. This value can be passed to sys.dm_exec_sql_text() to retrieve the associated text or object. 64 The 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, LoginSessionName will show Login1; while LoginName will show Login2. This column will display both SQL Server and Windows logins.