Neoview Repository User Guide (R2.4 SP1)

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 3-3 Comparison of ODBC Query Statistics and Query Runtime Statistics
Query Runtime StatisticsODBC 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.
VIEW NEO.HP_METRICS.ODBC_QUERY_STATS_V1_2400
This view preserves separate rows for data collected at the start and end of a query. If information
is not available for a field (because the record represents the start of a session and the field is not
populated until the end), the value in that field is NULL. To distinguish easily between start and
end records, you can filter results according to the value of STATEMENT_STATUS.
Character columns use ISO88591 or UCS2 encoding, as appropriate to the Neoview platform
configuration. If the platform is UCS2 or SJIS, all character columns are created with CHARACTER
SET UCS2. If the platform is ISO88591, all CHAR columns are created with CHARACTER SET
ISO88591.
The primary key for the ODBC_QUERY_STATS_V1_2400 field definition is SEGMENT_ID,
NODE_ID, SEQUENCE_NUM and the date/time fields (QUERY_EVENT_DATETIME_UTC and
other date fields).
Table 3-4 ODBC_QUERY_STATS_V1_2400 Field Definitions
DescriptionData TypeField Name
Segment number of the NDCS server
that reported the statistics.
INTEGER UNSIGNEDSEGMENT_ID
Processing node number of the NDCS
server which reported the statistics.
This is the node where the master
executor process which executed the
query was running.
INTEGER UNSIGNEDNODE_ID
ANSI SQL timestamp in Local Civil
Time when the statistics were
recorded in the Repository.
TIMESTAMP(6)QUERY_EVENT_DATETIME
36 Repository Views