Isolate Currently Executing SQL

book

Article ID: 49469

calendar_today

Updated On:

Products

CA RC/Migrator CA Endevor SCM Interface DB2 Administration CA RC Compare for DB2 for z/OS CA RC Extract for DB2 for z/OS CA RC/Query CA RC Secure for DB2 for z/OS CA RC Update for DB2 for z/OS CA Bind Analyzer for DB2 for z/OS CA Detector CA SQL-Ease for DB2 for z/OS CA Sysview Performance Management Option for DB2 for z/OS CA Database Detector for DB2 for z/OS CA Plan Analyzer for DB2 for z/OS CA Subsystem Analyzer for DB2 for z/OS CA Database Analyzer for DB2 for z/OS CA Fast Unload for DB2 for z/OS CA Fast Check for DB2 for z/OS CA Fast Index for DB2 for z/OS CA Fast Load for DB2 for z/OS CA Rapid Reorg for DB2 for z/OS

Issue/Introduction

Question: 

Is there a way, using Insight, to isolate SQL calls in a given program?

Answer: 

Yes, you can isolate the SQL calls in a given program. Insight Data Collector has to be running to monitor the SQL. In Chapter 7, page 20 of the Insight User Guide under the sub-heading of currently Executing SQL Panel, there is an example of SQL Text screen with the program being called on the Currently Executing SQL panel. With that information you can isolate SQL statements using the most resources and the plans they are running under and generate explain plans for those statements only. This will allow you to make rapid SQL tuning / table and/or index change recommendations more effectively than if you have to research every "bad" plan in the system.

Environment

Release:
Component: CIDB