The database administrator and security administrator should work together to assess database user needs, based on typical job functions, before creating users and granting user privileges.
|General users||Database end-users who only need to read the data or to run pre-existing queries or macros to generate reports.|
|Update users||Privileged users who perform some general user functions, and who also need to insert, update, or delete data, and create database objects.|
|Batch users||High-level users who typically perform batch-level functions such as:
|Database programmers||Users who design and create databases, tables, and views, as well as queries, macros and stored procedures for use by the user community. Programmers may require administrator privileges within a development database, while needing only limited privileges in the main production database.|
|Assistant administrators||Users who assist the principal administrator, user DBADMIN, created in Setting Up the Administrative Infrastructure. Assistant administrators may have most or all of the same privileges granted to user DBADMIN, but typically have a much smaller permanent space allocation because they have a limited ownership of objects.|
For information about the categories of users that exist in secure zones, see Implementing Teradata Secure Zones.