Permanent Space Allocations | Database Design | Teradata Vantage - 17.10 - Permanent Space Allocations - Advanced SQL Engine - Teradata Database

Teradata Vantage™ - Database Design

Advanced SQL Engine
Teradata Database
Release Number
July 2021
English (United States)
Last Update
Permanent data disk space includes database and user fixed PERM allocation. The database initialization routine creates these system users:
  • DBC (at the top of the hierarchy)
  • SYSTEMFE (owned by DBC)
  • SYSADMIN (owned by DBC)

All permanent space not consumed by SYSTEMFE and SYSADMIN is allocated to user DBC. The ramifications of the space allocation for each of the three system users are discussed in the subsections that follow.

System User DBC

The PERM space allocation of system user DBC is used for the following:

This DBC space… Performs this service … For this function …
PERM provides ownership Teradata production database space, which must accommodate the maximum PERM space allocated to each user and database by its creator.

The allocated space is used to store the rows in the data tables created by each user, including the following items.

  • Primary data table rows
  • Join index table rows
  • Hash index table rows
  • LOB and XML subtable rows
  • Secondary index subtable rows
  • Optional permanent journal image rows
  • Optional fallback rows, which replicate the rows of primary data tables, index subtables, hash and join index tables, and permanent journals
creates and maintains the WAL log/transient journal storing a before-image copy of every row affected by data modifications in all current sessions and Redo and Undo WAL records.
stores system table, index, macro, trigger, and view definitions setting up the data dictionary.
provides permanent space
  • Table headers.

    Note that each materialized global temporary table also requires a minimum of 512 bytes from the PERM space of its containing database or user for its table header.

  • CRASHDUMPS database.
TEMP provides temporary space data inserted into materialized global temporary tables.
SPOOL provides maximum defined SPOOL space per creator-defined allocation to each user and database
  • Dynamic allocation and release of intermediate and final result sets during query processing.
  • Volatile temporary tables.

System User SYSTEMFE

System user SYSTEMFE is owned by user DBC.SystemFE contains special macros and objects. The quantity of PERM space allocated to SYSTEMFE is minimal.

Only Teradata field support personnel normally log on under this user name.

System User SYSADMIN

System user SYSADMIN is owned by DBC.SysAdmin contains special views and macros. The quantity of PERM space allocated to SYSADMIN is minimal.

Only Teradata field support personnel normally log on under this user name.