16.10 - Creating a Table with Security Constraint Columns - Teradata Database

Teradata Database Security Administration

Product
Teradata Database
Release Number
16.10
Release Date
June 2017
Content Type
Administration
Security
Publication ID
B035-1100-161K
Language
English (United States)

You can define security constraint columns for both SET and MULTISET base tables using the CREATE TABLE statement. For example:

CREATE [SET|MULTISET] TABLE  table_name 
    (col1 integer, col2 integer, col3 varchar(30),
    Security_Classification CONSTRAINT, Job_Category CONSTRAINT)
    primary index(col1);

where Security_Classification (a hierarchical level constraint) and Job_Category (a non-hierarchical category constraint) are security constraint columns that match the names of existing security CONSTRAINT objects.

Tables need not be defined with both types of constraints.

A constraint column inherits the data type and the NULL/NOT NULL specification from the corresponding CONSTRAINT object.

You cannot specify the COMPRESS phrase for a security constraint column.