IBM has sunset their "Ready for DB2" program, but we're still ready to help you with DB2!
Determine Average Transaction Response Times
Within the average, compute
Time Distribution of time inside the database and out
For time owned by
the database, compute Time Distribution across resource consumers: CPU, read I/O, write I/O, direct I/O, Locks, and Sorts
Track Service Level Attainments and show how many, and what percent, of
transactions complete within defined service levels: Less than 1 second, less than 3 seconds, less than 5, 7, 10, 15, 30, and greater than 30 seconds
- Customer can modify threshold levels to suit their business needs
Adjustable time range selector makes it possible to see not only recent
results, but also rewind the hands of time to view history from earlier time periods
- Were SLAs met last week?
- Last month?
- Has database tuning been effective over time?
Integrated workflows with
make it easy to find database
statements that are causing SLAs to be missed due to high average elapsed times and statements that are contributing to resource bottlenecks such as high
CPU consumption, high I/O times, or high sort costs.