Long Runners

During day to day productive operation, there are always individual SQL commands which normally have long response times.

As tracefiles contain in dependency of the tracelevel all information available during the execution, QueryAdvisor provides the answer based on the preprocessing of this data.

A possible procedure might look as follows:

  1. Tracefiles are selected, either individually as file or as bulk from a directory, and loaded in the repository.
  2. Sorting takes place in the repository according to the selected criteria, such as, for example:
    a. Number of executions.
    b. Execution time (minimal/average/maximal).
    c. Cost (average runtime * number of executions).
    d. Number of execution plans.
  3. Selection of a specific SQL command, where upon
    a. in the right window, data relating to the individual execution with a drilldown in the tracefile and
    b. in the windows below in the individual tabs, where detailed information about the SQL command itself is available.
  4. Multiple execution plans are compared and assigned to individual executions.
  5. Drilldown for individual execution at the level of the appropriate tracefile.

QueryAdvisor trial.
QueryAdvisor in 30 Seconds

QueryAdvisor quote.
QueryAdvisor support forum.
QueryAdvisor Twitter channel.
social icons Facebook Twitter Blogspot RSS