Providing for a Permanent Journal - Advanced SQL Engine - Teradata Database

SQL Data Definition Language Detailed Topics

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
17.00
Published
June 2020
Language
English (United States)
Last Update
2021-01-24
dita:mapPath
jpx1556733107962.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1184
lifecycle
previous
Product Category
Teradata Vantage™

A permanent journal table is created and activated when the default JOURNAL table option and a journal table name are specified as part of the CREATE DATABASE, MODIFY DATABASE, CREATE USER, or MODIFY USER statement. See CREATE DATABASE, CREATE USER, MODIFY DATABASE, and MODIFY USER. The table resides in the database or user space that defined it. The specified JOURNAL parameters serve as the defaults for all the data tables created in that database or user space.

In defining a new table, you can override the established permanent journaling defaults by specifying the JOURNAL options as part of the CREATE TABLE statement. You can specify the journal table, the type of image (before-change, after-change, or both) and whether dual images are to be maintained for the created table, regardless of the option established when the containing database or user was created.

Whenever the structure of a table is altered, its version number increments. The following primary index changes qualify as changes to table structure:
  • Modification to its partitioning
  • Modification to its uniqueness
  • Modification to its column set definition

As a result of changing the version number for a table, permanent journal rollforward and rollback operations from previous table versions are no longer valid.

You can activate permanent journaling for existing tables using the ALTER TABLE statement. See ALTER TABLE (Basic Table Parameters), in particular, Activating Permanent Journaling.

Permanent journals are not supported for NoPI, column-partitioned, global temporary, or volatile tables.