<_locDefinition> <_locDefault _loc="locNone" /> <_locTag _loc="locData">DESCRIPTION <_locTag _loc="locData">BESTPRACTICE Cursors Collection of events produced when cursors are created, used and deleted. Database Collection of events that are produced when data/log files grow/shrink automatically. Errors and Warnings Collection of event classes that are produced when a SQL Server error or warning occurs (for example, an error during the compilation of a stored procedure, or an exception in SQL Server). Locks Collection of database object locking event classes. Objects Collection of event classes that are produced when database objects are created, opened, closed, dropped, or deleted. Performance Collection of showplan event classes and event classes that are produced from the execution of SQL data manipulation language (DML) operators. Scans Collection of database object scan event classes. Database objects that can be scanned include tables and indexes. Security Audit Collection of database audit event classes. Server Collection of server control and server memory change events. Sessions Collection of event classes that are produced by clients connecting to and disconnecting from SQL Server. Stored Procedures Collection of event classes that are produced by the execution of stored procedures. Transactions Collection of event classes that are produced by the execution of MS DTC or SQL transactions or by writing to the transaction log. TSQL Collection of event classes that are produced by the execution of SQL passed to SQL Server from the client. User configurable Collection of user configurable event classes. 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 Detects activity by all users connected to SQL Server before the trace was started; otherwise, these existing connections would not be detected by the Connect event class. 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 page, has been released. 24 Indicates acquisition of a lock on a resource, such as a data page. 25 Indicates that two concurrent transactions have deadlocked each other by trying to obtain incompatible locks on resources 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. 29 Describes the degree of parallelism assigned to the SQL statement. 30 Describes the degree of parallelism assigned to the SQL statement. 31 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. 48 Indicates when an object has been accessed, such as for a SELECT, INSERT, or DELETE statement. 49 Indicates when an object has been closed, such as at the end of a SELECT, INSERT, or DELETE statement. 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 SQL statement by ODBC, OLE DB or DB-Library. 54 Tracks when transaction are written to the transaction log. 55 Indicates that a hashing operation may have incurred a problem. 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. 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 Indicates when a cursor on an SQL statement has been prepared for use by ODBC, OLE DB or DB-Library. 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 SQL statement or statements have been executed by ODBC, OLE DB or DB-Library. 73 Indicates when a prepared SQL statement or statements have been unprepared by ODBC, OLE DB or DB-Library. 74 Indicates when a prepared cursor on an SQL statement has been executed by ODBC, OLE DB or DB-Library. 75 Indicates when a cursor on an SQL statement has been recompiled either intentionally or due to a schema change or other event. 76 Indicates when a cursor on an SQL statement has been converted by SQL Server from one type to another. 77 Indicates when a prepared cursor on an SQL statement has been unprepared by ODBC, OLE DB or DB-Library. 78 Indicates when a cursor on an SQL statement has been closed by ODBC, OLE DB or DB-Library. 79 Indicates that column statistics which would have been useful to the query optimizer are not present. 80 Indicates that a predicate joining two tables is not present. This can potentially result in long-running queries or inaccurate results. 81 Indicates when SQL Server memory usage increases or decreases by 1 megabyte or 5% of the maximum server memory, whichever is greater. 82 Collects event data defined by the user. 83 Collects event data defined by the user. 84 Collects event data defined by the user. 85 Collects event data defined by the user. 86 Collects event data defined by the user. 87 Collects event data defined by the user. 88 Collects event data defined by the user. 89 Collects event data defined by the user. 90 Collects event data defined by the user. 91 Collects event data defined by the user. 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. 97 Displays the query-plan with full compile-time details (including costing estimates and column lists) of the SQL statement being executed. 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. 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. 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. 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 (in milliseconds) taken by the event. 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.