15.00 - Summary - Teradata Database

Teradata Database Design

prodname
Teradata Database
vrm_release
15.00
category
User Guide
featnum
B035-1094-015K

Summary

The following table summarizes the Teradata Database features that do not support hash or join indexes.

 

              Feature

                    Reason Not Supported

              Recommended Workaround

Triggers

Triggers are handled by the Resolver, while hash indexes are handled by the Optimizer.

Do not define triggers and hash indexes on the same base tables.

Permanent journal recovery

Recovery process does not rebuild hash and join indexes.

Rebuild hash and join indexes after the permanent journal recovery completes.

MultiLoad

Utilities do not maintain hash and join indexes.

1 Ensure that no queries are running against tables that use the hash or join index to be dropped.

2 Drop hash and join indexes before loading or restoring the base tables.

3 Recreate hash and join indexes after loading or restoring the base tables.

FastLoad

Teradata Parallel Transporter LOAD and UPDATE operators

Archive/Recovery

  • NoPI tables
  • Column‑partitioned tables
  •  

    Hash indexes automatically add the primary index of their underlying base tables to their definition, and NoPI tables have no primary index.

    None.