Rules and Restrictions for the NORMALIZE Option
If a table definition contains such a column that is not included in the normalize_ignore_column_name list, Teradata Database aborts the request and returns an error to the requestor.
This action prevents a security issue that can occur if a constraint is specified on the beginning or end of a normalized Period column. In this case the input row violates the CHECK constraint but the normalized row does not. This situation cannot occur with UNIQUE constraints.
See “CREATE TABLE” in SQL Data Definition Language Syntax and Examples for information about the syntax used to created table columns.
See “ALTER TABLE (Basic Table Parameters)” on page 31 and “ALTER TABLE” in SQL Data Definition Language Syntax and Examples for information about modifying, adding, or dropping table columns.
See Security Administration for detailed information about row‑level security in Teradata Database.
See Teradata Unity Installation Guide and Teradata Unity User Guide for information about why you cannot use identity columns with Unity Director.