You can use the SYSCS_DIAG.STATEMENT_DURATION diagnostic table function to analyze the execution duration of the useful SQL statements in the derby.log file or a log file that you specify.
You can also use this diagnostic table function to get an indication of where the bottlenecks are in the JDBC code for an application.
For a database for which authentication and SQL authorization are both enabled, only the database owner can access this diagnostic table function. See "Configuring user authentication" and "Configuring user authorization" in the Derby Security Guide for more information.
To access the SYSCS_DIAG.STATEMENT_DURATION diagnostic table function, you must use the SQL table function syntax.
SELECT * FROM TABLE (SYSCS_DIAG.STATEMENT_DURATION()) AS T1where T1 is a user-specified table name that is any valid identifier.
You can specify a log file name as an optional argument to the SYSCS_DIAG.STATEMENT_DURATION diagnostic table function. When you specify a log file name, the file name must be an expression whose data type maps to a Java string.
SELECT * FROM TABLE (SYSCS_DIAG.STATEMENT_DURATION('somederby.log')) AS T1
The returned table has the columns shown in the following table.
Column Name | Type | Length | Nullable | Contents |
---|---|---|---|---|
TS | VARCHAR | 26 | false | The timestamp of the statement. |
THREADID | VARCHAR | 80 | false | The thread name. |
XID | VARCHAR | 15 | false | The transaction ID. |
LOGTEXT | LONG VARCHAR | 32,700 | true | The text of the statement or commit or rollback. |
DURATION | VARCHAR | 10 | false | The duration, in milliseconds, of the statement. |