SQL Logging by Workload Type | Teradata Vantage - SQL Logging by Workload Type - Advanced SQL Engine - Teradata Database

Database Administration

Product
Advanced SQL Engine
Teradata Database
Release Number
17.10
Published
July 2021
Language
English (United States)
Last Update
2021-07-27
dita:mapPath
upb1600054424724.ditamap
dita:ditavalPath
upb1600054424724.ditaval
dita:id
B035-1093
lifecycle
previous
Product Category
Teradata Vantageā„¢

SQL logging is based on the type of work being performed. In general, all Teradata Active EDW workloads can be broadly grouped into three categories as follows:

  • Short subsecond known work (Tactical Work)

    This workload can be identified by work typically done by TPUMP and single-AMP, subsecond tactical requests only.

  • Mostly long running work

    This workload can be identified by work typically done by Teradata Studio, Report Applications, MultiLoads, FastLoads, and BTEQ. It is typical mixed workload usage.

  • Mostly short subsecond requests (with occasional long running or unknown work)

    This workload can be identified by usage that is typically tactical (millions of short, subsecond queries), but there is an unknown factor, like unauthorized usage of the user ID, or a longer running component, that should be logged in a more detailed manner as to allow tuning or troubleshooting.