16.10 - LegacySpaceAcctg - Teradata Database

Teradata Database Utilities

Product
Teradata Database
Release Number
16.10
Published
June 2017
Language
English (United States)
Last Update
2018-04-26
dita:mapPath
zll1480972831047.ditamap
dita:ditavalPath
changebar_rev_16_10_exclude_audience_ie.ditaval

Purpose

Determines whether Teradata Database uses legacy or global space accounting. By default Teradata Database uses global space accounting.

  • Legacy space accounting makes cumulative space allocations to the AMPs that equal the maximum space value at allocation time, and the space limit for each AMP is set to the per-AMP quota. Teradata Database monitors the AMP space usage, and violations of space limitations are treated as exceptions, even if total use at the global database level is less than the maximum.
  • Global space accounting allows AMPs to temporarily utilize space beyond per-AMP maximum space values on an as-needed basis, provided the space utilization does not exceed the database maximum. Space allocations and de-allocations for AMPs happen dynamically as needed in the background as modifications are made to database and user tables. The amount by which AMPs can utilize extra space is determined by the SKEW option in CREATE DATABASE and CREATE USER statements, or by the system default settings defined by DBS Control fields DefaultPermSkewLimitPercent, DefaultSpoolSkewLimitPercent, and DefaultTempSkewLimitPercent.

Field Group

General

Valid Settings

Setting Description
TRUE Teradata Database uses legacy space accounting, and prevents creation of databases and users with non-zero SKEW values.

Additionally, ARC/DSA perm space errors during archive/restore operations cause the operations to abort.

FALSE Teradata Database uses global space accounting, and allows creation of databases and users with non-zero SKEW values.

Additionally, ARC/DSA perm space errors during archive/restore operations are ignored, allowing the operations to continue to run.

Default

FALSE

Changes Take Effect

After the DBS Control record has been written.

Changes to the value do not change the space accounting used for databases and users that were already created. If a database has been created with a non-zero SKEW value, it will use global space accounting and continue to do so, even if the value of LegacySpaceAcctg is subsequently changed to TRUE.

Usage Notes

  • Regardless of the field setting, databases and users created with a SKEW value of zero will use legacy space accounting.
  • The legacy space accounting method does not have the overhead of dynamic need-based space allocations. It is best suited when the database is expected to have uniform data distribution across all the AMPs in the system, or the global limit is set high enough to allow for variability in data distribution due to skew in the data.
  • The global space accounting method is best suited when the actual space usage is expected to be non-uniform across the AMPs.

Related Topics

For more information on... See...
the SKEW option for DDL, such as CREATE DATABASE and CREATE USER SQL Data Definition Language - Syntax and Examples.
related DBS Control fields