This
element indicates the number of SQL Data Definition Language (DDL)
statements that were executed.
Table 1. Snapshot
Monitoring InformationSnapshot Level |
Logical Data Grouping |
Monitor
Switch |
Database |
dbase |
Basic |
Application |
appl |
Basic |
For snapshot monitoring,
this counter can be reset.
Table 2. Event Monitoring InformationEvent Type |
Logical Data Grouping |
Monitor
Switch |
Database |
event_db |
- |
Connection |
event_conn |
- |
- Usage
- You can use this element to determine
the level of database activity
at the application or database level. DDL statements are expensive
to run
due to their impact on the system catalog tables. As a result, if
the value
of this element is high, you should determine the cause, and possibly
restrict
this activity from being performed.
You can also use this element
to
determine the percentage of DDL activity using the following formula:
ddl_sql_stmts / total number of statements
This information
can be useful for analyzing application activity and throughput. DDL
statements
can also impact:
- the catalog cache, by invalidating table
descriptor information and authorization
information that are stored there and causing additional system overhead
to
retrieve the information from the system catalogs
- the package
cache, by invalidating sections that are stored there and
causing additional system overhead due to section recompilation.
Examples of DDL statements are CREATE TABLE, CREATE
VIEW,
ALTER TABLE, and DROP INDEX.