Guidelines for Using Row Compression With Join Index Columns - Advanced SQL Engine - Teradata Database

SQL Data Definition Language Detailed Topics

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
17.00
Published
June 2020
Language
English (United States)
Last Update
2021-01-24
dita:mapPath
jpx1556733107962.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1184
lifecycle
previous
Product Category
Teradata Vantage™

A column set with a high number of distinct values cannot be row compressed because it rarely (and in the case of a primary key or unique index, never) repeats. Other column sets, notably foreign key and status code columns, are generally highly non-distinct: their values repeat frequently. Row compression capitalizes on the redundancy of frequently repeating column values by storing them once in the fixed part of the index row along with multiple repeated values in the repeated part of the index row. Typically, primary key table column values are specified as the repeating part and foreign key table columns are specified in the fixed part of the index definition.

See Teradata Vantage™ - Database Design, B035-1094 for more information about row compression for join indexes.