Join Indexes and the Optimizer - 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

For each base table in a query, the Optimizer performs certain processing phases to decide how a database operation that uses a join index is to be processed.

Phase Optimizer Behavior
Qualification The optimizer evaluates up to 10 join indexes to choose the one with the lowest cost.
Qualification for the best plan includes one or more of the following benefits:
  • Smallest size to process
  • Most appropriate distribution
  • Ability to take advantage of covered fields within the join index
Analysis of results The optimizer determines if this plan returns unique results, analyzing only those tables in the query that are used in the join index.
Subsequent action depends on analysis of the results:
  • If the results are unique, the Optimizer skips the sort-delete steps used to remove duplicates.
  • If the results are not unique, the Optimizer determines whether eliminating all duplicates can still produce a valid plan, recognizing any case where the following things are true:
    • No column_name parenthetical clause exists
    • All logical rows are accessed