There are many methodologies to help you. You can look at the slowest transactions on average and tackle those. You could look at those wait events that are the heaviest in time.
The problem with these approaches is that they are hit or miss. A slow transaction (that is, a SQL statement) that runs for 30 seconds may seem like an obvious choice. However, that statement can only run once. Whereas a transaction that executes 3 seconds on average and executes over 1000 times is a better choice for investigating performance.
Topics: Database Monitoring, Database Performance Products: Precise, Relational Database Performance Monitoring | IDERA Precise for Databases
Contact Sales
Join our email list and receive the latest case studies, event updates, product news, and much more.