PERMANENT, SPOOL, and TEMPORARY Space - 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™

You can define the maximum disk space available for various purposes for any database.

If necessary, the system changes the defined PERMANENT, SPOOL, or TEMPORARY disk space limits to the highest multiple of the number of AMPs on the system less than or equal to the requested space.

Global temporary tables require a minimum of 512 bytes from the PERM space of their containing database or user. This space is used for the table header of the table.

You should limit the amount of SPOOL space assigned to databases to a level that is appropriate for the workloads undertaken by its users. While some users require more spool space than others, you should minimize the allotment of spool for any database to a size that is large enough to permit result sets to be handled and space management routines such as MiniCylPack to run when disk space becomes low, but small enough to force spool overflow errors when runaway queries resulting from Cartesian products and other common SQL coding errors occur.

See Teradata Vantage™ - Database Design, B035-1094 and Teradata Vantage™ - Database Administration, B035-1093 for more information about user space.