17.10 - Using COPY and RESTORE After a Constraint Change - Advanced SQL Engine - Teradata Database

Teradata Vantage™ - Advanced SQL Engine Security Administration

Advanced SQL Engine
Teradata Database
Release Number
Release Date
July 2021
Content Type
Publication ID
English (United States)
Changing or deleting name:value pairs in a CONSTRAINT object after tables that contain the corresponding constraint column are archived may result in incorrect or unpredictable row level protection. Addition of new name:value pairs without changing existing constraint parameters does not have these unpredictable effects.

If the system determines that the constraint definition has a later timestamp (due to change) than the archive copy of the data used to COPY or RESTORE a row level security table, it issues a warning: Restored/Copied data table security may be compromised because a security constraint is inconsistent between the backup and disk. The COPY or RESTORE operation is allowed to complete, but security may be compromised.

Make sure you understand the possible security effects before you COPY or RESTORE a row level security table.