DBTELL

• An SQL query can be formulated many different ways.
• Small changes in the query can have enormous impact on how it performs, from agonizingly slow to lightning fast, and vice versa.
• The tables in the FROM clause, the AND/OR conditions, and the many keywords have crucial and often unexpected impact on performance.

When an SQL Query executes within SPUFI or in a program, what it does is hidden from view.

If you could see what a query is doing as it executes, you could use SPUFI – for example - to try out many forms of the query to see what works best. But a query is silent as it chugs along, and is mute until it returns its results.

DBTELL makes DB2 SQL performance visible as it executes - in SPUFI or in a program. DBTELL provides second-to-second feedback about the performance of an SQL query as it executes.

While a query is running, DBTELL tells you:

• What the query is doing second-by-second.
• What tables and indexes are being used.
• How many rows and pages are being scanned and changed.
• What sorts are being performed.
• What locks it is requesting and waiting for.

With DBTELL you can use SPUFI or SQL in a program to try out alternative forms of a query, and improve its efficiency and speed - because you can see what the query is doing second-by-second.

DBTELL un-silences SQL as it runs in SPUFI or in a program.

DBTELL Gives Immediate Feedback About z/OS DB2 SQL Queries

The SQL Queries are monitored:

• In programs
• Submitted via SPUFI

The results are shown immediately:

• As the queries are running
• On the programmer’s TSO screen
• In logs

A programmer uses DBTELL:

• WHILE developing an SQL strategy
• DURING program development

A small change or tweak in SQL can have an enormous impact on the time a query takes:

• From minutes to seconds, or seconds to minutes.

DBTELL is written FOR programmers and is easy to use