Relational Primary Index | Resource Usage Macros/Tables | Teradata Vantage - Relational Primary Index - Advanced SQL Engine - Teradata Database

Resource Usage Macros and Tables

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
17.00
Published
June 2020
Language
English (United States)
Last Update
2021-01-23
dita:mapPath
fwg1557098454552.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1099
lifecycle
previous
Product Category
Teradata Vantage™

All resource usage tables have the same nonunique primary index of TheDate, TheTime, and NodeID columns.

The primary index is nonunique because:
  • Of rows that will appear with the same timestamp during daylight savings time.
  • Some tables have multiple rows per logging period.
  • Rows that have duplicate timestamps can be distinguished by the GmtTime column.

Because the primary index is nonunique, all resource usage tables are created as MULTISET tables. This prevents the system from checking for duplicate rows.

For more information on MULTISET tables, see “CREATE TABLE (Table Kind Clause)” in Teradata Vantage™ - SQL Data Definition Language Syntax and Examples, B035-1144 or “Duplicate Rows in Tables” in Teradata Vantage™ - SQL Fundamentals, B035-1141.