Detects and corrects performance issues on DB22017-01-19T11:43:42+00:00

Detects and corrects performance issues on DB2

How to determine which packages or statements are responsible for heavy workload

Analyze application workload to optimize performance and CPU usage

With the explosion of packaged solutions, e.g. SAP/R3® and PeopleSoft® etc., and their many-thousands of tables exploited by dynamic SQL, the ability of performance specialists to effectively tune the application or SQL becomes virtually impossible. Packaged vendors will always endeavor to provide a reasonable set of indexes for these products, but each site’s individual implementation and use of these tools can be quite different and thus require alternative indexes and very often far fewer. Such analysis is a time-consuming and daunting task since it requires you to review individual SQL of an application for predicate usage and simultaneously take business priorities into account.

Administration and development teams often lack the specific information they require to make such critical decisions.

Benefits

  • Detects the top resourcing “crunchers” by analyzing complete applications and reducing their “workload“.

  • Captures traces for all SQL regardless of origin, both static and dynamic SQL, including QMF® or ERP packages.

  • Uses a very “lite” DB2 trace to locate the top “n” resources at alternative levels. Levels may be THREAD, PACKAGE, PACKSUM or SQL statements (static / dynamic or both).

  • Tunes critical SQL statements with DB/IQ QA.

  • Tunes critical indexes with DB/IQ IA+.

Features

  • Filters SQL Monitor data to display critical packages and SQL, e.g. execution frequency of SQL and/or package, elapsed time, CPU time, rows processed, stage I or II rows processed, pages retrieved, etc.

  • User-defined threshold values to locate packages and/or SQL statements with the highest-total, average or single DB2® elapsed time, CPU time, no. of scanned pages, exec counts, etc.

  • Detects critical objects by reporting which tables and / or indexes were the most frequently accessed and how.

What you can do

LEARN MORE