Administrative Users | Teradata Vantage - 17.20 - Working with Administrative Users - Analytics Database - Teradata Vantage

Teradata Vantage™ - Analytics Database Security Administration - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-03-07
dita:mapPath
hjo1628096075471.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
zuy1472246340572

All Teradata Vantage sites should have at least one user with clearly defined administrative duties.

Teradata recommends that you divide administrative duties between the security administrator and the database administrator, regardless of the number of administrators at your site.

User DBC should create both the database administrator and security administrator users, and should allocate DBC disk space that is not needed for system functions to the administrative users. Then the administrative users can create lower level administrators and other database users, and allocate space to them.

When administrators create users and databases, a hierarchical relationship results.



DBC directly creates the security administrator (A) and database administrator (B) users. DBC is the immediate owner (parent) of A and B, and owns everything in the hierarchy.

The security administrator (A) owns database (C) and assistant administrator (D), and then creates end user (F) in database (C).
  • A is the immediate owner, or parent, of C and D.
  • C is the immediate owner, or parent, of F.

The database administrator (B) creates database (E). B is the immediate owner of E.

Owners have implicit privileges on the objects they own. See Ownership Privileges.