General - Advanced SQL Engine - Teradata Database
ANSI Temporal Table Support
- Product
- Advanced SQL Engine
- Teradata Database
- Release Number
- 17.10
- Published
- July 2021
- Language
- English (United States)
- Last Update
- 2021-07-27
- dita:mapPath
- kit1592007446534.ditamap
- dita:ditavalPath
- kit1592007446534.ditaval
- dita:id
- B035-1186
- lifecycle
- previous
- Product Category
- Teradata Vantage™
- Valid time is the Teradata implementation of what ANSI calls “application time.”
- The valid_start and valid_end columns must be defined as NOT NULL.
- The data types of the valid_start and valid_end columns must match.
- To function as a temporal table, the valid-time table must be defined AS VALIDTIME. System-time tables do not have valid time.
- A table can have only one valid-time period definition.
- A valid-time table cannot be a queue, error, or global temporary trace table.
- Statistics cannot be collected on the valid-time derived period column, but they can be collected on the component start and end time columns.
- Algorithmic compression (ALC) is not allowed on DateTime columns that act as the beginning and ending bound values of a temporal derived period column.