Effects of Join Indexes - Teradata Vantage

Teradata® VantageCloud Lake

Deployment
VantageCloud
Edition
Lake
Product
Teradata Vantage
Published
January 2023
Language
English (United States)
Last Update
2024-04-03
dita:mapPath
phg1621910019905.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
phg1621910019905
  • MultiLoad and FastLoad Utilities
    You cannot use these utilities to load or unload data into base tables on which a join index is defined, because join indexes are not maintained during the execution of these utilities. If an error occurs because of a join index, take these steps:
    • Make sure that any queries that use the join index are not running.
    • Drop the join index. (The system defers completion of this step until there are no more queries running that use the join index.)
    • Load the data into the base table.
    • Recreate the join index.
  • TPump Utility

    You can use the TPump utility, which performs standard SQL row inserts and updates, to load or unload data into base tables with join indexes, because TPump properly maintains join indexes during execution. However, performance may improve by dropping join indexes on the table before the load and recreating the join indexes after the load.

  • Permanent Journal Recovery

    Using a permanent journal to recover a base table (that is, ROLLBACK or ROLLFORWARD) with an associated join index defined is permitted. The join index is not rebuilt during the recovery process, but is marked nonvalid and must be dropped and recreated before being used again in the execution of queries.