16.10 - Working with Administrative Users - Teradata Database

Teradata Database Security Administration

Teradata Database
Release Number
Release Date
June 2017
Content Type
Publication ID
English (United States)

All Teradata Database 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.

For a list of duties, see:

For setup suggestions, see:

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.