15.00 - Rules and Restrictions for the NORMALIZE Option - Teradata Database

Teradata Database SQL Data Definition Language Detailed Topics

Product
Teradata Database
Release Number
15.00
Content Type
Programming Reference
Publication ID
B035-1184-015K
Language
English (United States)

Rules and Restrictions for the NORMALIZE Option

  • The column you specify for the NORMALIZE option must have either a Period data type or be a derived Period column.
  • If you do not specify an explicit normalization condition, the default is ON MEETS OR OVERLAPS.
  • If a table that is to be normalized contains columns with a BLOB, CLOB, JSON, or XML data type, those columns must be explicitly specified in the normalize_ignore_column_name list 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.

  • Teradata Database validates both UNIQUE and PRIMARY KEY constraints with normalized rows. If a normalized row violates a UNIQUE or PRIMARY KEY constraint, Teradata Database aborts the request and returns an error to the requestor.
  • Teradata Database validates CHECK constraints on a row inserted into a normalized table, and if the constraint is violated, the system 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.

    Related Topics

    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.