Permanent journals store configured before and/or after images of changes, not whole-table snapshots before each transaction. Transient journaling also records recovery information for changes rather than an upfront copy of the entire table.
Part of the Teradata Internals and Operations guide.
Journaling can be implemented at the table or database level. Even if database-level journaling is enabled, individual tables can have journaling disabled by setting a different value in the table’s DDL statement.
One permanent journal can be utilized for every database.
Permanent journaling enables you to revisit the past and utilize an “UNDO” option.
Get the complete Teradata tuning book, free
Teradata Query Performance Tuning: The DWHPro Guide
By Roland Wenzlofsky & Artemios Vogiatzis
206 pages on statistics and demographics, access paths and indexes, query execution plans, and joins. Get the full PDF and practical Teradata updates from DWHPro.
Confirm your email to receive your download link. Privacy policy. Unsubscribe in any newsletter.
About the free bookPermanent journaling complements a recovery and backup strategy. It does not justify skipping backups; recovery depends on journal configuration, retention, a suitable baseline and supported recovery procedures.
Before/after image selection, single/dual journaling and fallback protection are separate configuration choices. Verify their interaction for the release and table definition.
Although permanent journaling offers some data protection, it is important to note that journal tables require the same amount of space per row as the underlying permanent table.
Determine on a case-by-case basis which tables should be used to store permanent journal records.
The following is an illustrative journal DDL template, not a tested recovery procedure. The metadata query executed in the audit but returned no rows; undo, rollforward and journal-DDL behavior were not exercised.
CREATE SET TABLE <DATABASE>.<TABLE>
,FALLBACK ,
NO BEFORE JOURNAL,
AFTER JOURNAL,
WITH JOURNAL TABLE = <OTHER_DATABASE>.<MYJOURNAL> ,
CHECKSUM = DEFAULT
(
PK INTEGER NOT NULL
) PRIMARY INDEX ( PK );
Use the following statement to retrieve a comprehensive list of journal tables that are currently accessible within the system:
SELECT * FROM DBC.JOURNALS;
Deciding what to change in your data platform?
Compare optimisation, modernisation and migration against your workload and business requirements.
Get the complete Teradata tuning book, free
Teradata Query Performance Tuning: The DWHPro Guide
By Roland Wenzlofsky & Artemios Vogiatzis
206 pages on statistics and demographics, access paths and indexes, query execution plans, and joins. Get the full PDF and practical Teradata updates from DWHPro.
Confirm your email to receive your download link. Privacy policy. Unsubscribe in any newsletter.
About the free book