Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Tue, 28 Mar 2006 @ 11:24:03 GMT

  <Prev Next>   <<First <Prev Next> Last>>  

Subj:   Re: Tablesize Vs allspace
From:   Cappelli, Andrea

Cause the DBC.allspace include the "ALL" table permspace.

The "All" table represents all tables that reside in the user's space. The MaxPerm figure for "All" is the amount of permanent space defined for that user.


MaxPerm is the maximum number of bytes available for table, index, and permanent journal storage in a system database or user.

The number of bytes specified is divided by the number of AMP vprocs in the system. The result is recorded on each AMP vproc and may not be exceeded on that vproc.

Perm space limits are deducted from the limit set for the immediate parent of the object defined.

Perm space is acquired when data is added to a table. The space is released when you delete or drop objects.


PeakPerm is the largest number of bytes ever actually used to store data in a user or database. This value is maintained on each AMP vproc.

You can reset the PeakPerm value to zero by using the ClearPeakDisk Macro supplied in User DBC.

  <Prev Next>   <<First <Prev Next> Last>>  
  Top Home Privacy Feedback  
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 15 Jun 2023