Relational Primary Index | Resource Usage Macros/Tables | Teradata Vantage - Relational Primary Index - Analytics Database - Teradata Vantage

Resource Usage Macros and Tables

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-10-30
dita:mapPath
efj1628112349534.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
wqp1472240716284
lifecycle
latest
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 the information about the CREATE TABLE (Table Kind Clause) statement in Teradata Vantage™ - SQL Data Definition Language Syntax and Examples, B035-1144 or the information about duplicate rows in tables in Teradata Vantage™ - SQL Fundamentals, B035-1141.