Analyze Statistics Results
The Statistics tab of the Run Time pane in the SQL Optimizer window shows the statistics the accumulative totals for the CPU Time, Scan Count, Logical Reads, Physical Reads, and APF I/Os from the execution of the SQL statement. To see the individual values for the statistics by table, click All Records or First Record on the top right pane or the Statistics tab at the bottom of the SQL Optimizer window.
For more information about this statistics see the Adaptive Server Performance Tuning: Monitor and Analyzing manual, Chapter 4.
|
Statistics
(All Records and First Record) |
Description |
|
Elapsed Time |
The execution time (in clock time) that it takes the SQL statement to select all records or the first record. This figure may include time that Adaptive Server spent on processing other tasks or waiting for disk or network I/O to complete. This is the accumulative run time for the SQL statement. The individual values for the Elapsed Time can be view by clicking All Records or First Record on the top right pane of the SQL Optimizer window. |
|
CPU Time |
The CPU Time is accumulative total for the CPU time to execute the SQL statement. The individual values for the CPU time can be view by clicking All Records or First Record on the top right pane of the SQL Optimizer window. |
|
Actual I/O Cost |
This Actual I/O Cost is a calculate combining the Logical and Physical I/O statistics after it was executed in the Batch Run or the Run Time function. |
|
Writes |
The Writes is the total number of buffers written to the disk. |
|
Scan Count |
The Scan Count represents the number of times a query accessed a particular table. |
|
Logical Reads |
The Logical Reads represents the accumulative total for logical read for each table and index used in the SQL statement. |
|
Physical Reads |
The Physical Reads represents the accumulative total for logical read for each table and index used in the SQL statement. |
|
APF IOs used |
The APF (Asynchronous-PreFetch) IOs used is the I/O the server does in advance anticipating which pages will need to be read next, so that the pages will be in cache when the process actually tries to access them. |
Related Topic
Analyze Time and Statistics Results
View Analyze Statistics Window