15.10 - Volatile Tables - Teradata Database

Teradata Database SQL Data Definition Language Detailed Topics

prodname
Teradata Database
vrm_release
15.10
category
Programming Reference
featnum
B035-1184-151K

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” on page 559 and “Nonpartitioned NoPI Tables” on page 532.

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
  • Otherwise, the options for volatile tables are identical to those for global temporary tables.

    When you create an unqualified volatile temporary table, the login user space is used as the default database for the table, whatever the default database is currently specified to be.

    When you create a qualified volatile table, the database name you specify must be identical to that of the login 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” on page 474. Also, see Database Design and the DBS Control utility in Utilities.