Note: In a future release, the XMLTextInfo column in DBQLXMLTbl will change its data type from VARCHAR to CLOB type casted to Teradata XML type. To ensure your applications remain compatible with this future enhancement, Teradata recommends using the QryLogXMLDocV view instead of QryLogXMLV.
This view of DBQLXMLTbl shows query plans and statistics usage information in an XML document. This view combines multiple rows of XMLTextInfo with the same QueryID into a single XMLTextDoc document.These BEGIN QUERY LOGGING or REPLACE QUERY LOGGING options populate the QryLogXMLDocV view:
|
QryLogXMLDocV Field |
Description |
|
CollectTimeStamp |
Date and time that the rows were written to the database. This field is also part of the multicolumn NUPI (see also ProcID). For more information on CollectTimeStamp, see “Comparing CollectTimeStamp Value Between Tables” on page 380. |
|
DetailedStatsEnabled |
Possible values include: |
|
HasDetailedStatsData |
Possible values include: |
|
HasStatsUsageData |
Possible values include: |
|
HasVerboseData |
Possible values include: |
|
HasXMLPlanData |
Possible values include: |
|
ProcID |
Unique processor ID of the Dispatcher and part of the multi-column NUPI (also see CollectTimeStamp). |
|
QueryID |
Internally generated unique identifier of the query. |
|
StatsUsageEnabled |
Possible values include: |
|
VerboseEnabled |
Possible values include: |
|
XMLDocType |
Describes the type of content stored in column XMLTextInfo. This column contains an encoded 32-bit integer value whose bit positions describe the type of data in the associated XML document stored in the XMLTextInfo column. The XML DocType bit mask values are: Note: It is easier to use the [Option] Enabled and Has [Option] columns to see this information. Queries against these columns allow you to specify a Y or N value instead of bit-mapped values. |
|
XMLPlanEnabled |
Possible values include: |
|
XMLTextDoc |
Combines multiple XMLTextInfo rows with the same QueryID into a single XML document as Teradata XML type. |