A Repository configuration can support ODBC query statistics, query runtime statistics, or both.
By default, both are enabled. 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 3-1 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 statement 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.

Overview