Creating the Database Administrator Profile - 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™

Profiles define the system resources available to member users, and can also set password control parameters.

  1. Log on to the database as user DBC.
  2. Create the profile for the database administrator, user DBADMIN, for example:
    CREATE PROFILE AdminProfile AS
    SPOOL =spool_space 
    TEMPORARY =temp_space 
    ACCOUNT = ’account’ ;

    where:

    Field Description
    AdminProfile Required. The name of the database administrator profile.

    Recommendation: Administrative procedures in this publication use the name AdminProfile for the database administrator profile.

    User DBADMIN is the only member of this profile. Because of space and ownership concerns, you should create one or more separate profiles for other administrative users.
    spool_space Optional. The amount of space available for intermediate query results or formatted answer sets to queries and volatile tables. The system borrows spool space from unused permanent space anywhere in the system.

    Recommendation: Set this value equal to the amount of space in the Spool_Reserve database defined in Working with System-Level Space Allocation.

    temp_space Optional. Required only when you use global temporary tables, volatile tables and other features that require temporary space.

    Recommendation: Specify a value if the database requires use of temporary space. For information, see Teradata Vantage™ - Database Administration, B035-1093 and Teradata Vantage™ - Database Design, B035-1094.

    'account' Optional.

    Account strings are an optional method of controlling the granularity of resource accumulations that are reported in the DBC.Acctg table. Account strings allow the collection of CPU and I/O that is reported in DBC.Acctg to be grouped by application time of day, and priority. Variable substitution parameters included in the account string will be resolved at execution time.

    A secondary use of account strings is to direct the classification of a query to a default Timeshare workload in TASM or TIWM. This classification will be effective only in cases where normal classification processes do not match the query to a user-defined workload.

    An account string defines the following characteristics for profile member sessions in the database:
    • Session priority
    • Account ID (to assign charges for system time and resources)
    • Date stamp
    • Time stamp

    Recommendation: Define at least one account string per profile. If necessary, you can add other accounts later using a MODIFY PROFILE statement.

    For more information about accounts, see Teradata Vantage™ - Database Administration, B035-1093.