All of the details shown in the Tablespace Details pane are listed below in alphabetic order. This pane is available on the Dynamic SQL Details sub drilldown for the Dynamic SQL tab in the Top SQL drilldown.
Initially, details are shown in Spotlight's default order. You can sort and arrange them in different ways using options on the right-click menu for column headers.
|
Statement Detail |
Value |
|
Rows Deleted Internally |
The number of rows deleted from the database due to internal activity caused by a SQL statement. The activity can occur when the statement activates triggers on the table being referenced. It can also occur due to a cascading delete that enforces an ON CASCADE DELETE referential constraint. If the number of internal deletes is high, check to see whether the triggers and constraints defined for the table are necessary. |
|
Rows Updated Internally |
The number of rows updated in the database due to internal activity caused by a SQL statement. The activity can occur when the statement activates triggers on the table being referenced. It can also occur due to a SET NULL row update that enforces an ON DELETE SET NULL referential constraint. If the number of internal updates is high, check to see whether the triggers and constraints defined for the table are necessary. |
|
Rows Inserted Internally |
The number of rows inserted in a database due to internal activity caused by a SQL statement. The activity occurs when the statement activates triggers on the table being referenced. If the number of internal inserts is high, check to see whether the triggers defined for the table are necessary. |
|
Rows Read |
The number of rows read from the table referenced by a statement. These are rows that are read to return query results and not rows returned to the application. A high number could mean that a table would benefit from additional indexes. |
|
Rows Written |
The number of rows changed (inserted, deleted, or updated) in the table referenced by a statement. The number includes rows for temporary tables generated by the database manager in order to execute the statement. |
|
Statement Sorts |
The number of sorts performed on the data retrieved by a statement. It includes sorts of temporary tables generated by the database manager in order to execute the statement. A high number of sorts could mean that an index is in order. Indexes can reduce the need to sort data. |
|
Sort Overflows |
The number of sort overflows for a statement. These are sorts that ran out of sort heap and might have required disk space for temporary storage. The I/O required in writing to disk imposes additional overhead. |
|
Sort Time (msec) |
The amount of time spent on sorts for a statement. It includes sort time for temporary tables created by the database manager in order to execute the statement. A long sort time could mean that a statement would benefit from tuning or that an index is needed to reduce the need to sort data. |
|
User CPU Time (microsec) |
The user CPU time used by a statement. The time is shown in microseconds. A long user CPU time could mean that a statement would benefit from tuning. |
|
System CPU Time (microsec) |
The system CPU time used by a statement. The time is shown in microseconds. A long system CPU time could mean that a statement would benefit from tuning. |
|
Elapsed Time (microsec) |
The elapsed execution time for a statement. Time is shown in microseconds. |
|
Stats Fabricate Time (msec) |
The total time (in milliseconds) required by the statement's latest real-time statistics collection to generate statistics based on metadata controlled by the index and data manager. |
|
Sync Runstats Time (msec) |
The total time (in milliseconds) used on activities triggered during the statement's latest real-time synchronous RUNSTATS execution. |
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center
