ALTER TABLE and Fallback | Teradata Vantage - ALTER TABLE and FALLBACK - Analytics Database - Teradata Vantage

SQL Data Definition Language Detailed Topics

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-07-11
dita:mapPath
vuk1628111288877.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
B035-1184
lifecycle
latest
Product Category
Teradata Vantage™

When an ALTER TABLE request adds FALLBACK, the operation generates a full-table scan. To add FALLBACK to a table, all AMPs must be online and operational.

When a table or join index is partitioned, its fallback rows are partitioned the same as its primary data rows. If the primary data rows have a primary index, the fallback data rows have the same primary index. If the primary data rows do not have a primary index, the fallback data rows do not have a primary index.

You can change the FALLBACK properties of a global temporary table definition if and only if there are no materialized instances of that table anywhere in the system. However, when an instance of a global temporary table is materialized, Vantage creates it without fallback irrespective of its definition unless there is a down AMP in the system. In that case, and that case only, the table is materialized with fallback if it has been defined to do so.

To enable the file system to detect all hardware read errors for tables and join indexes, set CHECKSUM to ON.