Limits for Join Indexes - Teradata VantageCloud Lake

Lake - Database Reference

Deployment
VantageCloud
Edition
Lake
Product
Teradata VantageCloud Lake
Release Number
Published
February 2025
ft:locale
en-US
ft:lastEdition
2025-11-21
dita:mapPath
ohi1683672393549.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
ohi1683672393549
  • Tables can have up to 32 secondary and join indexes.

    These 32 indexes can be any combination of secondary and join indexes, including the system-defined secondary indexes used to implement PRIMARY KEY and UNIQUE constraints.

    Each multicolumn NUSI that specifies an ORDER BY clause counts as two consecutive indexes in this calculation.

  • Index columns cannot have XML, BLOB, CLOB, JSON, ARRAY, or VARRAY.
  • Join index columns can have Period data types and can include expressions composed of system and user-defined functions and methods, including the use of the BEGIN, END, and P_INTERSECT built-in functions on a Period data type column to compose an expression in the projection list and a single-table condition in its WHERE or ON clauses.
  • Join indexes can be created on a row-level security-protected table only if all of the following criteria are met.
    • The join index references a maximum of one row-level security-protected table.
    • All of the row-level security constraint columns in the indexed table are included in the join index definition.