About Assigning Security Constraints - Advanced SQL Engine - Teradata Database

Security Administration

Product
Advanced SQL Engine
Teradata Database
Release Number
17.05
17.00
Published
September 2020
Language
English (United States)
Last Update
2021-01-23
dita:mapPath
ied1556235912841.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1100
lifecycle
previous
Product Category
Teradata Vantageā„¢

You can assign up to 6 hierarchical (non-set) constraints and 2 non-hierarchical (set) constraints to a user or profile. You must specify at least 1 name:value pair for each constraint.

Each assigned CONSTRAINT object must exist in the database, and the assigned security label values must correspond to valid name:value pairs defined in the object.

When more than one hierarchical label value is assigned to a user or profile, you can include the keyword DEFAULT after the label to specify that it is the default value for user sessions. If DEFAULT is not specified, the first constraint name listed in the user/profile definition is the default. DEFAULT is not applicable to non-hierarchical security constraints.

If a user is the member of a profile that assigns one or more security constraints, the assignments in the profile supersede any assignments made directly to the user.