Neoview Repository User Guide (R2.4 SP1)

up to 16000 characters. If the complete query text is written across multiple rows,
FRAGMENT_NUMBER is incremented for each row, starting with 0.
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 SQL_TEXT_VW1 field definition is QUERY_ID and FRAGMENT_NUMBER.
Table 3-2 SQL_TEXT_VW1 Field Definitions
DescriptionData TypeField Name
Primary Key
A unique identifier for this SQL
statement, generated by Neoview SQL
compiler.
CHAR(160) NO DEFAULTQUERY_ID
Primary Key
Number of the row for a section of
query text, starting with zero (0). 16000
characters of query text are written per
row.
SMALLINT UNSIGNED NO
DEFAULT
FRAGMENT_NUMBER
Name of the Neoview platform
segment used by the datasource to
connect and start the query. The
Master Executor process for the query
is running in this segment.
CHAR(16) DEFAULT NULLSEGMENT_NAME
Neoview system name, made up of the
first three letters of the system name,
followed by 01 for the first platform at
your site, 02 for the second platform
at your site, and so on. For example,
NEO01.
CHAR(64) DEFAULT NULLPLATFORM_NAME
Complete SQL Text for a query. 16000
characters are written per row.
TIP: The full SQL text can be joined
to the query statistics by joining on the
QUERY_ID field.
VARCHAR(16000) DEFAULT NULLSQL_TEXT
Query Statistics for Release 2.4
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.
To access current query statistics with only a single row per query, use these views:
• “VIEW NEO.HP_METRICS.QUERY_STATS_VW1” (page 22)
• “VIEW NEO.HP_METRICS.SQL_TEXT_VW1” (page 34)
The following table lists the major differences between ODBC and query runtime statistics.
Query Statistics 35