HP Neoview Release 2.4 Software - Manual (Page 25)

Table 3-2 ODBC_QUERY_STATS_V1 Field Definitions (continued)
Description Data Type Field Name
Compiler-provided value, one of:
SQL_SELECT_UNIQUE,
SQL_SELECT_NON_UNIQUE
SQL_INSERT_UNIQUE,
SQL_INSERT_NON_UNIQUE,
SQL_UPDATE_UNIQUE,
SQL_UPDATE_NON_UNIQUE,
SQL_DELETE_UNIQUE,
SQL_DELETE_NON_UNIQUE,
SQL_CONTROL,
SQL_SET_TRANSACTION,
SQL_SET_CATALOG,
SQL_SET_SCHEMA, SQL_OTHER,
SQL_UNKNOWN,
SQL_CALL_NO_RESULT_SETS,
SQL_CALL_WITH_RESULT_SETS,
SQL_SP_RESULT_SET,
SQL_NOT_SUPPORTED. For
definitions of SQL statement types,
see the Neoview SQL Reference
Manual. For example, to find
information about
SQL_SET_TRANSACTION, look up
the SET TRANSACTION statement
in the Neoview SQL Reference Manual.
The suffix _UNIQUE indicates that
the statement operates on a single
row. The suffix _NON_UNIQUE
indicates that the statement could
operate on multiple rows. In the
START row for an ExecuteDirect
query, the value of this field is always
SQL_UNKNOWN; in the END row,
it has its proper value. CHARACTER(36) or NCHAR(36) STATEMENT_TYPE
A unique ID for the query, beginning
with the string “MXID” and
including, among other elements a
unique query number, delimited by
underscores, and an ODBC-generated
statement ID. If an error occurred
before the query launched, the value
in this field is the text . For
more information, see
“Format of the
Query ID Field” (page 25) .
VARCHAR(160) or NCHAR
VARYING(160) QUERY_ID
Text of the query. If the length
exceeds 3200 bytes, the Repository
will contain multiple rows, with
ascending values in the
SEQUENCE_NUM field. VARCHAR(3200) or NCHAR
VARYING(3200) SQL_TEXT
Format of the Query ID Field
The query ID has the following format:
MXIDversion segment node pin processStartTS sessionNum unLen userName
snLen sessionName
2 digits version number of ID version
3 digits segment number segment
Query Statistics 25