17.10 - Limits on Applying Security Constraints to Tables - 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)

A maximum of 5 security constraints can be defined for a table.

A security constraint column cannot be part of a primary index or a partitioning expression, but can participate in a secondary index.

Join indexes and hash indexes must include all constraint columns in the base table.

Limits on CHECK or UNIQUE table constraints:

  • If a table protected by row level security is defined with a CHECK or UNIQUE constraint, enforcement of the constraint bypasses any security constraints defined for the table.
  • You cannot define a CHECK or UNIQUE constraint on a security constraint column.

Do not define row level security on a parent or child referential integrity (RI) table.

If either or both the parent and child RI tables define security constraint columns, the security constraint UDFs are disabled and execution of any request that accesses either of the RI tables continues as if the tables had no row level security constraints.