Usage Notes - Advanced SQL Engine - Teradata Database

SQL Operators and User-Defined Functions

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
Published
January 2021
Language
English (United States)
Last Update
2023-04-27
dita:mapPath
xwv1596137968859.ditamap
dita:ditavalPath
hoy1596145193032.ditaval
dita:id
B035-1210
lifecycle
previous
Product Category
Teradata Vantage™
  • You can reduce the analysis time for a query log by limiting it to queries that fall within a specified LogStartTime and/or LogEndTime. If the specified LogStartTime is NULL, the analysis reads from the start of the query log. If the specified LogEndTime is NULL, the analysis reads to the end of the query log.
  • If LogDatabase is NULL, tables are grouped by database.
  • For LogDatabases other than DBC and PDCRDATA, user TDMaps must be granted the SELECT privilege on its query log tables prior to calling AnalyzeSP.
  • All generated actions from a call to AnalyzeSP are associated with the common identifier OutputActionList, which cannot have a NULL value. The recommended actions are written as rows to table TDMaps.ActionsTbl. Action types are limited to ALTER and EXCLUDE.
  • Analysis recommendations identified by OutputActionList can be passed as an input parameter to ManageMoveTablesSP, which executes the recommended actions.
  • If the OutputActionList value corresponds to an action list that already exists in the actions table, an error occurs.
  • If there is no query log data, tables are grouped by database. If a log database is specified but there is no log data, then each table belongs to its own group, essentially not grouping anything.
  • If the output parameter NumLogEntries returns a value of 0, the query log suggests actions to take.
  • Error tables (created by CREATE ERROR TABLE) are added to ActionsTbl following the base table.