AFTER JOURNAL - Teradata VantageCloud Lake

Lake - Working with SQL

Deployment
VantageCloud
Edition
Lake
Product
Teradata VantageCloud Lake
Release Number
Published
February 2025
ft:locale
en-US
ft:lastEdition
2025-11-21
dita:mapPath
jbe1714339405530.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
jbe1714339405530

The type of permanent journal image to maintain for the table. Any existing images are not affected until the table is updated.

If you specify the JOURNAL keyword without also specifying NO or DUAL, Vantage maintains a single copy of the image unless FALLBACK is in effect or is also specified.

If you specify journaling for a database that uses fallback protection by default, Vantage maintains DUAL images.

You cannot add or modify journal options for an nonpartitioned NoPI table or for a column-partitioned table.

NO
After-change images are not maintained for the table.
DUAL
Two after-change images are maintained for the table.
LOCAL
Single after-image journal rows for non-fallback data tables are written on the same virtual AMP as the changed data rows.
NOT LOCAL
Single after-image journal rows for non-fallback data tables are written on another virtual AMP in the compute cluster.