Volatile Tables - Analytics Database - Teradata Vantage

SQL Data Definition Language Detailed Topics

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-07-11
dita:mapPath
vuk1628111288877.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
B035-1184
lifecycle
latest
Product Category
Teradata Vantage™

The primary index for a volatile table can be nonpartitioned or row-partitioned. The table can also be defined without a primary index (NoPI). See Partitioned and Nonpartitioned Primary Indexes and Nonpartitioned NoPI Tables.

The following options are not permitted for volatile tables:
  • Referential integrity constraints
  • CHECK constraints
  • Permanent journaling
  • DEFAULT clause
  • TITLE clause
  • Named indexes
  • Column partitioning
  • Primary AMP index
  • Column with a DATASET data type that includes the WITH SCHEMA option

Otherwise, the options for volatile tables are the same as those for global temporary tables.

When you create an unqualified volatile temporary table, the logon user space is used as the default database for the table, regardless of the default database that is currently specified.

When you create a qualified volatile table, you must specify the logon user database. Otherwise, the system returns an error.

For information about how block-level compression works with volatile tables, see Block-Level Compression and Tables. Also, see Teradata Vantage™ - Database Design, B035-1094 and the DBS Control utility in Teradata Vantage™ - Database Utilities, B035-1102.