Can You Help Beta-test DBTELL DB2 SQL Monitor?
Akiva Lane
Java, AWS, Cobol, DB2, z/OS Assembler, Linux, Legacy Modernization - wrote DB2/SQL and z/OS performance monitors called DBTELL and LOOK.
DB2 Monitors gather data to help DBA’s get a global and micro view of DB2 resources and problems so that they can fix inefficiencies. Small changes in SQL queries can make dramatic differences in how tables are joined, indexes are used, and sorts are performed. Performance monitors are essential tools for DBA’s to make sure that DB2 systems run efficiently.
There is one problem with DB2 Monitors: they are used after systems are already developed, at the end of the program development cycle.
DBTELL is a tool that is used by a programmer during development. The programmer decides how to formulate the SQL queries while writing the program – for example what tables to join and what indexes to use, and in what order to produce the results. Small differences in the query can result in vast differences in performance.
DBTELL gives immediate feedback to the programmer WHILE writing the program, and WHEN those initial decisions are made about HOW to craft the access strategy for each query.
From the TSO screen, the programmer has two ways to test the performance of a query.
- Use SPUFI to try the query
- Run a program with the query
When DBTELL is told to monitor a user or plan, DBTELL writes on the TSO screen and/or a log what the query is doing second-by-second. The programmer can watch in real-time the result of the query decisions, and immediately can try alternatives. It is common that small changes and tweaks can reduce the time the query takes from 30 seconds to 2 seconds.
DBTELL tracks and monitors SQL that run as part of a program, or that are submitted with tools such as SPUFI.
Here is an example of DBTELL output.
This information can be written to your TSO screen or to a log file or both. When written to a log file, each line includes additional information such as Job Name/Userid, Plan Name, DB2 subsystem, date and time, so a sort can be used to extract specific information.
DBTELL first displays the SQL query. Then it shows information in the following columns:
DBTELL also writes a separate line for each time a sort starts and ends, and when a lock is gotten and released.
If you are interested in helping us out by giving us your valuable feedback and beta-testing DBTELL – free now, and for an eventual 50% discount – contact [email protected]
Looks like an interesting opportunity, when you consider existing quite expensive products available