Creating Account Strings - Teradata Database

Teradata Database Administration

Teradata Database
Release Number
English (United States)
Last Update
Product Category

Creating Account Strings

Teradata recommends that you devise an account system and then identify the accounts required for various groups in the user community before attempting to specify account information in user profiles. An account string is limited to 128 characters.

User account strings should follow this format:


Note: If a CREATE or MODIFY statement specifies more than one account string, the individual strings must be separated by commas and the entire list of strings enclosed by parentheses.





Required Account String Variables


Optional. The performance group identifier. Priority scheduler uses the identifier to determine the priority of the session.

Recommendation: Specify one of the following instead of $G0+:

  • $R0+ = Rush
  • $H0+ = High
  • $M0+ = Medium (default)
  • $L0+ = Low
  • Note: Consider the following when specifying the performance group.

  • The 0 specification designates resource partition 0, the default.
  • The + character is a place holder that forces the account_ID to start at the fifth character, which is important for compatibility with certain administrative tools.
  • account_ID

    The account name. Uniquely identifies the account.

    Recommendation: You can use the four characters of the account_ID to differentiate accounts and to provide an abbreviated description of the account function.

    For example:

  • A department, such as finance (FIN) or marketing (MKT)
  • A job function, such as general use (G), update (U), or batch processing (B).
  • A complete account ID might resemble one of the following:

    FINB or MKTU

    Note: Although more characters are allowed, using a four-character account_ID maintains application compatibility.

    Account String Expansion (ASE) Variables

    Teradata Database tags the session with information specified by the ASE variables for later use in management of database sessions. Each ASE variable expands to the number of characters needed to express the related information. The string limit is enforced against the expanded form.

    Specification of the ASE variables shown below is optional, but recommended. Other variables are available. For information, see “Logging Resource Usage Data with Account String Variables” on page 160.


    The ampersand (&) designates an account string expansion (ASE) variable. Teradata Database automatically replaces these variables with actual values upon opening the session. You can use any or all of the following:

  • &S = the session number
  • &D = the date
  • &H = the time
  • &D