Académique Documents
Professionnel Documents
Culture Documents
Index Teradata 14
By: Smarak Das
Employee ID: 391485
Index
----------------------------------------------------------------------------------------------------------------------------------------------- 03
References ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- 20
Covering Join Index substitute for the base table(s) and Partially Covering
Join Index part-substitute and part-point to base tables.
3
Query access the Join Index, rather than accessing and possibly, joining
the base tables.
The decision to use Join Index instead of the base tables rests with the
Optimizer only.
Statistics plays an important role for Optimizer to choose the Join Index
rather than the base tables.
4
The Join Index joins with the base tables for retrieving the additional
columns referenced in the query and not available in the Join Index. Such
operation provides better query optimization than scanning the base tables
for all the columns specified in the query.
Joining with base tables occurs only if ROWID, UPI, USI of the base
tables has been specified as columns of the Join Index.
5
When ROWID is used, the Join Index is joined with the base tables via ROWID Join.
When UPI or USI is used, the Join Index is joined with the base tables via Merge Join.
The keyword ROWID is a System-Derived Column and can only be used in the Join
Index definition.
The following exceptions are applied for Join Index inheriting the
compression of base tables:
The Primary Index columns of Join Index are not compressed.
The Partition Primary Index columns of Join Index are not compressed.
The Aggregate Columns of Join Index are not compressed.
The Columns in the Order By clause of Join Index are not compressed.
update has been used in generic context to include the delete and update operation
performed by DELETE, MERGE & UPDATE statements.
10
11
14
Hash Index
Structures sharing properties with Single Table Join Index or Secondary Indexes.
Hash Index provides easier creation and deletion feature with few factors
contributing towards to its essence as compared to Single Table Join Index or
Secondary Index.
Hash Index puts in double duty by providing pointers to base tables to facilitate
situations where the index doesnt cover the query fully. These pointers are
transparently added as Primary Index columns by Teradata.
Key difference between Hash Index and Secondary Index is that Hash Index
Partition Key is user selectable.
16
Both Join Index & Hash Index are maintained implicitly by Teradata.
Both allows Statistics Collection.
Both can be Hash-Ordered or Value-Ordered.
Both can be Fallback Protected.
Both cannot use PARTITION column.
Both share restrictions with FastLoad, MultiLoad, Archive/Recovery Utility.
Both cannot be directly queries or updated.
17
It allows Partitioning.
It is compatible with NoPI Tables.
Hash Index
It allows Single Table only.
It doesnt inherit Compression
from the base tables.
18
Hash Index
References
Teradata Database Design PDF
Teradata Forums
Teradata Magazine Online