Modifying Row Partitioning Defined with an Updatable DATE, CURRENT_DATE, or CURRENT_TIMESTAMP - Teradata Vantage

Teradata® VantageCloud Lake

Deployment
VantageCloud
Edition
Lake
Product
Teradata Vantage
Published
January 2023
ft:locale
en-US
ft:lastEdition
2024-12-11
dita:mapPath
phg1621910019905.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
phg1621910019905

Vantage provides a special version of the ALTER TABLE statement for modifying the row partitioning of a table (or WHERE clause of a join index definition) defined with an updatable DATE, updatable CURRENT_DATE, or updatable CURRENT_TIMESTAMP built-in function called ALTER TABLE TO CURRENT (see ALTER TABLE TO CURRENT Usage Notes).

ALTER TABLE TO CURRENT reconciles the values of these functions when specified in a partitioning expression of a table or join index or in the WHERE clause of a join index.

The rules for ALTER TABLE TO CURRENT are identical for row partitioning and column partitioning. However, using ALTER TABLE TO CURRENT on a table or join index with column partitioning and row partitioning can negatively impact performance, because moving a row from one row partition to another can be costly.

See the table in Comparing ALTER TABLE TO CURRENT and ALTER TABLE … REVALIDATE for a comparison of the capabilities of ALTER TABLE … REVALIDATE PRIMARY INDEX requests with the ALTER TABLE TO CURRENT statement.