AFTER JOURNAL - Teradata Vantage - Analytics Database

SQL Data Definition Language Syntax and Examples

Deployment
VantageCloud
VantageCore
Edition
VMware
Enterprise
IntelliFlex
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
ft:locale
en-US
ft:lastEdition
2025-11-06
dita:mapPath
jco1628111346878.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
mdr1472255012272
lifecycle
latest
Product Category
Teradata Vantage™

Type of image to be maintained by default for data tables created in the new database. The JOURNAL keyword without AFTER implies BEFORE and AFTER images.

If only AFTER JOURNAL is specified, then a before change image is not maintained. If both types are specified, the two specifications must not conflict.

You can override this setting for individual tables when the table is created. See CREATE TABLE and CREATE TABLE AS.

DUAL
If journaling is specified, a DUAL journal is maintained for data tables with FALLBACK protection.
LOCAL
Single after-image journal rows for non-fallback data tables are written on the same virtual AMP as the changed data rows. See the CREATE DATABASE “Local Journaling” topic in Teradata Vantage™ - SQL Data Definition Language Detailed Topics, B035-1184.
NOT LOCAL
Single after-image journal rows for non-fallback data tables are written on another virtual AMP in the cluster than the changed data rows.
NO
The default is no journaling.