Secondary, Hash, and Join Index Limits
Parameter |
Value |
Number of tables that can be referenced in a join. |
128 |
Minimum number of secondary, hash, and join indexes, in any combination, per base data table. |
0 |
Maximum number of secondary, hash, and join indexes, in any combination, per base data table. Each composite NUSI defined with an ORDER BY clause counts as 2 consecutive indexes in this calculation. The number of system-defined secondary and single-table join indexes contributed by PRIMARY KEY and UNIQUE constraints counts against the combined limit of 32 secondary, hash, and join indexes per base data table. |
32 |
Maximum number of columns referenced per secondary index. |
64 |
Maximum number of columns referenced per single table in a hash or join index. |
64 |
Maximum number of rows per secondary, hash, or join index. |
Limited only by disk capacity. |
Maximum number of columns referenced in the fixed part of a compressed join index. Teradata Database implements a variety of different types of user‑visible compression in the system. When describing compression of hash and join indexes, compression refers to a logical row compression in which multiple sets of nonrepeating column values are appended to a single set of repeating column values. This allows the system to store the repeating value set only once, while any nonrepeating column values are stored as logical segmental extensions of the base repeating set. |
64 |
Maximum number of columns referenced in the repeating part of a compressed join index. |
64 |
Maximum number of columns in an uncompressed join index. |
2,048 |
Maximum number of columns in a compressed join index. |
|