The Objects event classes can be used to monitor when an object such as a database, table, index, view, or stored procedure is opened, created, deleted, or used.
Event class | Description |
---|---|
Object:Closed | Open object has been closed, such as at the end of a SELECT, INSERT, or DELETE statement. |
Object:Created | Object has been created, such as for CREATE INDEX, CREATE TABLE, and CREATE DATABASE statements. |
Object:Deleted | Object has been deleted, such as for DROP INDEX and DROP TABLE statements. |
Object:Opened | Object has been accessed, such as for SELECT, INSERT, or DELETE statements. |
By monitoring the Object:Opened event class, you can determine which objects are most commonly used. The Object:Created and Object:Deleted event classes can be used to determine if many ad hoc objects are being created or deleted, for example, by ODBC applications that often create temporary stored procedures. By monitoring the SQL User Name and NT User Name default data columns in addition to the Objects event classes, you can determine the name of the user who is creating, deleting, or accessing objects. This can be useful when monitoring to determine if your security policies are correctly implemented, for example, to confirm that users who are not allowed to create or delete objects are not doing so.
Because object events are so prolific, capturing the object event classes can incur significant overhead on the server being traced and result in large trace files or trace tables.
These are the event-specific data columns for the Objects event category.
Event class | Data column | Description |
---|---|---|
Object:Closed | Event Sub Class | Object type |
Object ID | Object that was closed | |
Object:Created | Event Sub Class | Object type. |
Object ID | Object that was created | |
Object:Deleted | Event Sub Class | Object type |
Object ID | Object that was deleted | |
Object:Opened | Event Sub Class | Object type |
Object ID | Object that was opened |
Overview of Creating and Maintaining Databases