You can define the maximum amount of disk space available for various purposes for any Teradata user.
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, as outlined by the following table:
|IF you do not define this type of space for the user …||THEN the system-assigned space is the largest value that meets both of the following criteria …|
You should limit the amount of SPOOL space assigned to users to a level that is appropriate for the workloads undertaken by each user. While some users require more spool space than others, you should minimize the allotment of spool for any user 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.