Containers and Space - Teradata Vantage

Teradata® VantageCloud Lake

Deployment
VantageCloud
Edition
Lake
Product
Teradata Vantage
Published
January 2023
ft:locale
en-US
ft:lastEdition
2024-12-11
dita:mapPath
phg1621910019905.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
phg1621910019905

The data in a column-partitioned table can be stored in containers or subrows. The following table defines these terms.

If Vantage can pack a large number of column partition values into a container, this form of compression, called row header compression, can reduce the space needed for a column-partitioned table or join index compared to the same object without column partitioning.

If Vantage can pack only a small number of column partition values in a container because of their width, there can be a small increase in the space needed for a column-partitioned table or join index compared to the same object without column partitioning. ROW format may be more appropriate.

A small number of column partition values and a large number of column partitions can cause a large increase in the space needed for a column-partitioned object compared to the same object without column partitioning. The space required for a table can increase by 24 times.

Consider making one of the following changes:

  • Alter the column or row partitioning to allow for more column partition values per combined partition.
  • Remove the column partitioning from the table or join index.