background image
<< EMPTY_RIGHT_ROWS | CONSTRUCTOR_TIME >>

SYSXPLAIN_RESULTSET_TIMINGS system table

<< EMPTY_RIGHT_ROWS | CONSTRUCTOR_TIME >>
Derby Reference Manual
249
Column Name
Type
Length
Nullable
Contents
common situations
which involve sorting
of the data are when
processing the ORDER
BY and GROUP BY
clauses.
STMT_ID
CHAR
36
false
This column will contain
the ID value which
identifies the particular
statement for which
this result set was
executed. Note that
there may be multiple
result sets executed
for a single statement,
so a join between the SYSXPLAIN_STATEMENTS
table and the SYSXPLAIN_RESULTSETS
table may retrieve
multiple rows.
TIMING_ID
CHAR
36
true
If statistics timings were
not being captured,
this column will have a
NULL value. If statistics
timings were being
captured, this column
will contain the id value
which can be used as a
foreign key to join with
the SYSXPLAIN_RESULTSET_TIMINGS
row which has the
timing information for
this resultset.
SYSXPLAIN_RESULTSET_TIMINGS system table
The SYSXPLAIN_RESULTSET_TIMINGS table captures timing information about
result set accesses which occurred during statements that were executed using
RUNTIMESTATISTICS with XPLAIN style.
See "Working with RunTimeStatistics" in Tuning Derby for information on
how to configure this. Note that statistics timing must be configured by calling
SYSCS_UTIL.SYSCS_SET_STATISTICS_TIMING(1). Each row in this table describes
various timing information for this particular result set in this particular statement.
Rows in this table are typically joined with rows in SYSXPLAIN_STATEMENTS and
SYSXPLAIN_RESULTSETS during analysis. For example:
select rs.op_identifier, rst.execute_time
from my_stats.sysxplain_resultsets rs,
my_stats.sysxplain_resultset_timings rst
where rs.stmt_id = ? and
rs.timing_id = rst.timing_id
order by rst.execute_time desc