Row Distribution - 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

Database rows are hashed across a table’s AMPs using the row hash value of their primary index or primary AMP index as the hash key. This does not apply for the rows of NoPI tables.

Vantage also uses the row hash of a primary index or primary AMP index to retrieve a row. The following graphic shows how a row is hashed and assigned to an AMP:


How a row is hashed and assigned to an AMP

By carefully choosing the primary index or primary AMP index for each table, you can make sure that rows that are frequently joined hash to the same AMP, eliminating the need to redistribute the rows across the BYNET to join them.

The following graphic shows how you can set up rows from commonly joined tables on the same AMP to make sure that a join operation avoids being redistributed across the BYNET:


Commonly joined tables on the same AMP