The following table summarizes recommended system conditions to measure.
| System Conditions | What to Use | What to Collect | How to Use |
|---|---|---|---|
| Response time | Heartbeat queries |
|
Saved samples can be used to:
|
| Baseline testing |
|
|
|
| Database Query Log (DBQL) | Application response time patterns | Track trends:
|
|
| Resource utilization | Resource Usage |
|
Look for:
|
| AMPUsage | CPU seconds and I/O for each unique account | Use this to quantify heavy users. | |
| DBQL | CPU, I/O, spool used, rows returned | ||
| Data growth |
|
Summary row per table once a month | Look at trends. |
| Changes in data access | DBQL | Summary row per table and the number of accesses once a month | Look for increases in access, trends. |
| Increase in the number of active sessions | LogOnOffV, acctg | Monthly and summarized number of sessions | Look for increases in concurrency and active users. |
| Increase in system demand | DBQL | Query counts and response times, plus other query information | Look for trends, including growth trends, and measure against goals. |
| Resource Usage | System demand | ||
| AMPUsage | Queries with errors or queries that have been canceled |