User does performance monitor and finds:
We are noticing that TOAD query is kicking off an additional TOAD query and acquires one connection for SYSIBM.SQLSTATISTICS ref GDR BCU E3 UDB 9.1.
typically the second non related query is of format:
SELECT TABLE_CAT, TABLE_SCHEM, TABLE_NAME, NON_UNIQUE, INDEX_QUALIFIER, INDEX_N
AME, SYSIND.TYPE, ORDINAL_POSITION, COLUMN_NAME, CASE WHEN ASC_OR_DESC='I' THEN NULL ELSE ASC_OR_DESC END AS ASC_OR_DE
SC, INTEGER(CARDINALITY) AS CARDINALITY, PAGES, FILTER_CONDITION
FROM SYSIBM.SQLSTATISTICS SYSIND
WHERE TABLE_SCHEM = 'VDW02 ' AND TABLE_NAME = 'CORP_TRANS_DTL_BILLED' AND ( NON_UNIQUE = 0 OR NON_UNIQUE IS NULL ) ORDER BY 4,7,5,6,8
In a second connection\screen using Quest\TOAD the above connection is reused for the same SYSIBM.SQLSTATISTICS reference.
e.g. First time 1 connection for user SQL ; 1 connection for SYSIBM.SQLSTATISTICS ; total 2 connections
second query 2 connections for user (assuming different editor session selected) and reuse existing connection for SYSIBM.SQLSTATISTICS; total 3 connections
Just means more connections and redundant work happening than needed?
One another comment to add.
The Query thats shown below from sysibm.sqlstatistics if you notice is starting exactly the second the actual query finishes up.
Information Time_Created Time_Started Time_completed
Actual Query execution 2012-02-15-188.8.131.520000 2012-02-15-184.108.40.2060000 2012-02-15-220.127.116.112905
This is from the query ... from sysibm.sqlstatistics 2012-02-15-18.104.22.168000 2012-02-15-22.214.171.124000 2012-02-15-126.96.36.1999567
Enhancement request CR 98,434 has been submitted to Development for consideration in a future release of Toad for DB2.