AFTER JOURNAL - Advanced SQL Engine - Teradata Database

SQL Data Definition Language Syntax and Examples

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
Published
January 2021
Language
English (United States)
Last Update
2021-01-22
dita:mapPath
ncd1596241368722.ditamap
dita:ditavalPath
hoy1596145193032.ditaval
dita:id
B035-1144
lifecycle
previous
Product Category
Teradata Vantage™

After-image journal rows are maintained by default for data tables created in the new user.

A user can contain only one journal table.

The default is no journaling.

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.

This setting can be overridden for a particular data table when the table is created (see CREATE TABLE and CREATE TABLE … AS).

Specifying the JOURNAL keyword without also specifying either NO or DUAL implies single copy journaling.

If journaling is specified, a DUAL journal is maintained for data tables with FALLBACK protection.

The JOURNAL keyword without AFTER implies both types (BEFORE and AFTER) of images.

NO
After-image journal rows are not maintained by default for data tables created in the new user.
DUAL
Dual after-image journal rows for non-fallback data tables are maintained.
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 cluster.