The DBQLSQLTbl table is populated if you specify the WITH SQL option in addition to default information. The WITH SQL option causes DBQL to attempt to log the full statement text, no matter how large, into the DBQLSQLTbl table. Multiple rows are generated as necessary.
Row Values
The following table lists the populated fields in a DBQLSQLTbl row.
|
DBC.DBQLSQLTbl Field |
Description |
|
CollectTimeStamp |
Time that the rows were written to the database. This field is also part of the multi-column NUPI (see also ProcID). For more information on CollectTimeStamp, see “Comparing CollectTimeStamp Value Between Tables” on page 380. |
|
ProcID |
Unique processor ID of the Dispatcher and part of the multi-column NUPI (also see CollectTimeStamp). |
|
QueryID |
Internally generated identifier of the query. Note: QueryID is a system-wide unique field; You can use QueryID to join DBQL tables or the DBC.TdwmExceptionLog table with DBQL tables without needing ProcID as an additional join field. |
|
SQLRowNo |
Row number of the statement. Value is 1 unless the statement is large and requires multiple rows. |
|
SQLTextInfo |
A full SQL text segment, a string of up to approximately 32,000 characters. Note: BTEQ has a limited column length. Use Teradata SQL Assistant or Teradata Studio to display longer lengths. Note: If SQLTextInfo has more than one row per QueryID, use the QryLogSQLDoc[V] view to see a single, readable document per QueryID. For more information, see “Improving SQL Text Readability” on page 313. |