17.10 - Creating a Table with Security Constraint Columns - Advanced SQL Engine - Teradata Database

Teradata Vantage™ - Advanced SQL Engine Security Administration

Product
Advanced SQL Engine
Teradata Database
Release Number
17.10
Published
July 2021
Language
English (United States)
Last Update
2022-02-15
dita:mapPath
ppz1593203596223.ditamap
dita:ditavalPath
wrg1590696035526.ditaval
dita:id
zuy1472246340572

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.