Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.


Share this Page URL
Help

6.3: Database Monitor query examples > Rows with retrieved or fetched details - Pg. 170

QQRID We only focus on row types 3000, 3001, and 3002, which contain query optimizer index suggestions. QQI2 This column indicates the importance of a statistic. QVC1000 This column contains the statistics identifier. This query attempts to correlate the SQE advised statistics to the query optimizer index suggestions. The idea is that we should attempt to build indexes for cases where an index can be used by the query optimizer for the data access method. If an index is solely used for statistical purposes, the advantage should be given to SQE statistics due to their low maintenance overhead. An exception to this recommendation is if statistics must be current at all times. The only way to accomplish this is by having an index set with the *IMMED maintenance attribute. 6.3.14 Rows with retrieved or fetched details Specifying *DETAIL in the TYPE parameter of the STRDBMON command indicates that detail rows, as well as summary rows, must be collected for fetch operations. The same is true for detailed the SQL Performance Monitor in iSeries Navigator. The purpose of detailed 3019 row is for tuning non-SQL queries, those which do not generate a QQ1000 row, such as OPNQRYF. For non-SQL queries, the only way to determine the number of rows that are returned and the total time to return those rows is to collect detail