beautypg.com

Query statistics for r2.4 sp1, Query statistics for pre-r2.4 sp1 – HP Neoview Release 2.5 Software User Manual

Page 101

background image

Query Statistics for R2.4 SP1

Three new Repository views improve the collection of the Repository statistics:

Two new Repository views allow you to access compilation and execution (runtime) statistics
in one place without having to join rows or use multiple views:

“VIEW NEO.HP_METRICS.QUERY_STATS_VW1” (page 89)

provides access to all query

statistics, including new query statistics metrics

“VIEW NEO.HP_METRICS.SQL_TEXT_VW1” (page 32)

provides access to the full SQL

query text if longer than 254 bytes.

Query statistics:

A new Repository view—

“VIEW NEO.HP_METRICS.EVENTS_VW1” (page 45)

—allows you

to use SQL to query information collected from the event message logs. Events from these
logs on all segments are available through this single view.

Event messages:

All data in the Repository is now stored for 30 days.

Query Statistics for Pre-R2.4 SP1

The following table lists the major differences between ODBC and query runtime statistics.

NOTE:

Many of the differences reflect features of Neoview Workload Management Services

(WMS). For information about that product, see the Neoview Workload Management Services Guide.

Table E-2 Comparison of ODBC Query Statistics and Query Runtime Statistics

Query Runtime Statistics

ODBC Query Statistics

Monitors queries managed by WMS.

Monitors queries from ODBC and JDBC.

Execution metrics are updated while the query is running.
Data for finished queries is stored in the Repository.

Execution metrics become available at the end of the
query.

Includes additional query data, such as disk process busy
time, query elapsed time, execution start and end times
(when available), node utilization percentages, and busy
times for various processes involved in query execution.

Includes only information supplied by the NDCS (ODBC,
JDBC) server and available through Neoview event
services.

Provides all query information in a single row.

Different views provide separate rows of data at the start
and end of query, or consolidate data in a single row.

Query completion statistics might not be available from
the runtime statistics data source. In this case, the final
statistics are the last received from WMS.

Query completion statistics are provided by the NDCS
server when the query completes.

SQL text is not available.

SQL text is available.

Service name is available.

Data source name is available.

Data is available only for queries monitored by WMS.
(WMS monitors only NON_UNIQUE queries.)

Data is available for all queries, whether unique or
non-unique.

Synchronized with QueryRTS entity in Neoview
Management Dashboard.

Not synchronized with query data in Neoview
Management Dashboard.

Query statistics data, which was collected before Release 2.4 SP1 was installed, remains in the
original Repository tables. To access the old Repository data, use these Repository views:

NEO.HP_METRICS.ODBC_QUERY_STATS_V1_2400

NEO.HP_METRICS.ODBC_QUERY_STATS_V2_2400

NEO.HP_METRICS.QUERY_RUNTIME_STATS_V1_2400

These three views provide access to R2.4 query and runtime statistics information. This information
is maintained on the Neoview platform for your convenience, but it will not change, nor are the
tables maintained. These three views use the pre-R2.4 SP1 "two rows per query" semantics of
query statistics.

Query Statistics for R2.4 SP1

101