QryLogTDWM[V] is the Teradata Dynamic Workload Management view of the main log table, DBQLLogTbl. The following table describes the fields in QryLogTDWM[V].
|AcctString||The account string at the time the row was committed. Because accounts can be changed dynamically at the query or session level, this may not be the same account that:
|CollectTimeStamp||A date and time unique to each buffer cache, which changes for each new buffer. Part of the multi-column NUPI for the table (see also ProcID).
This time will be set when the cache is ready to receive new data, not when rows are written to the database.
For more information on CollectTimeStamp, see Comparing CollectTimeStamp Value Between Tables.
|DefaultDatabase||Name of the default database for the query.|
|DelayTime||The seconds a query was delayed by the Teradata dynamic workload management software.|
|ExceptionValue||Specifies what type of Teradata dynamic workload management software exception occurred.|
|FinalWDID||Indicates the number of the workload definition in which the query completed execution.|
|FinalWDName||Indicates the name of the workload definition in which the query completed execution.|
|Flex Throttle||Whether TASM released the request because of dynamic (flex) throttles, which relax workload throttle limits when the system is less busy. If flex throttles released the request, the value is T. If not, the value is NULL.|
|InternalRequestNum||The internal request number.
For commands, other than those within a stored procedure, the internal request number and the number in the RequestNum field will be the same.
For stored procedures invoked within a session, the internal request number increments by 1 for every request made by the stored procedure. This means that RequestNum will be the request number of the CALL and the value in InternalRequestNum will continue to increment for all other queries issued by the session.
|LastStateChange||Time of the last State change by the Teradata dynamic workload management software.|
|LogicalHostID||Unique identifier of the logon source for the logged query. A value of 0 indicates an internal session.|
|LSN||The Logon Sequence Number used for a load utility.|
|MinRespHoldTime||The number of seconds the request was held to meet the minimum response time.|
|TotalFirstRespTime||Total time (in seconds) from when the request was submitted to when the first response was sent. Includes DelayTime and MinRespHoldTime.|
|NoClassification||Indicates if the query was not classified.|
|OpEnvID||The internal identifier of the Operating Environment/Planned Environment currently enforced by the Teradata Dynamic Workload Management software.|
|OpEnvName||The name of the Operating Environment/Planned Environment currently enforced by the Teradata Dynamic Workload Management software.|
|ProcID||Unique processor ID of the Dispatcher and part of the multi-column NUPI for the table (see also CollectTimeStamp).|
|ProfileName||The name of the profile associated with the query.|
|QueryID||Internally generated identifier of the query.|
|RequestNum||Unique identifier of the query.
The request number for the commands that occur within a stored procedure CALL statement will all appear as the same number of the CALL statement itself. For more information on request numbers for stored procedures, see note for ExpandAcctString.
|ResponseTimeMet||Indicates if the query met service level goals.|
|SessionID||Unique session identifier.|
|SessionWDID||Workload ID class associated with the session. It determines the priority of the session when the TDWM workload classification is active.|
|SessionWDName||Workload name associated with the session.|
|StatementGroup||If there is a DDL statement in a request, StatementGroup reports which type:
If the statement has only one DML statement or multiple DML statements that are all of the same type, StatementGroup will indicate the type. For example if there are three DELETE statements in a request, StatementGroup will report:
Similarly, for requests with individual or multiple INSERT, INSERT... SELECT, UPDATE or SELECT statements, StatementGroup will report:
In a multistatement request with different types of DML statements, you will see a list showing the number of statements of each type in the request. For example, a request with one insert and two update statements will appear as:DML Del=0 Ins=1 InsSel=0 Upd=2 Sel=0
|SysConID||The internal identifier of the System Condition (SysCon)/ System Health currently enforced by the Teradata Dynamic Workload Management software.|
|SysConName||The name of the System Condition (SysCon)/ System Health currently enforced by the Teradata Dynamic Workload Management software.|
|TDWMAllAmpFlag||Indicates whether one of the steps of the query is an all-amp step. This is used to classify a query into a workload definition.|
No longer a TASM rule attribute. The letter 'N' will always be logged.
|TDWMEstLastRows||The estimated last row count generated by the Optimizer used to classify a query into a workload definition.|
|TDWMEstMaxRows||The estimated maximum row count generated by the Optimizer used to classify a query into a workload definition.|
|TDWMEstMaxStepTime||TDWM estimated maximum step time.|
|TDWMEstMemUsage||The estimated memory used by the request (in megabytes). It represents the largest step in the request.|
|TDWMEstTotalTime||The total estimated time of a query by the Teradata dynamic workload management software (based on Optimizer estimates) and applied against rules read from the TDWM database.
This time is reported in milliseconds in DBC.DBQLogTbl, but it is reported in seconds in the view DBC.QryLogTDWM[V].
|TDWMRuleID||Rule identifier of the query.|
|UserID||The unique ID of the user whose query is logged.|
|UserName||Name under which the session being logged was initiated.|
|WDID||The workload definition number assigned to the query.|
|WDName||The workload definition name assigned to the query.|
|WDOverride||Indicates if the workload definition assignment was overridden.|