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

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:
    CREATE PROFILE admin_profile AS
    [ SPOOL = spool_space ]
    [ TEMPORARY = temp_space ]
    [ ACCOUNT = 'account' ];
    admin_profile
    The name of the database administrator profile (for example, DBADMIN).
    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.
    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 runtime.
    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 is 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.