One or more accounts to be assigned to the user. See About Accounts.
For example: ‘ $P 0+account_ID &S&D&H ’
Account strings defined in the user profile supercede the accounts defined in the user definition.
If you do not specify an account string for the user or the user profile, the user inherits the first account string that is defined for the immediate owner of the user (another user or a database).
Users with multiple accounts can access a non-default account by specifying the account in:
- The logon string.
- A SET SESSION ACCOUNT statement.
For a user to specify an account in the logon string or in a SET SESSION ACCOUNT statement, the account must be assigned in the user or profile definition for the user.
- Each position in an account string has a specific meaning and format requirement. See Creating Account Strings.
- Each account_string must follow the standard Teradata Database naming rules, and must be enclosed by APOSTROPHE characters. A list of account_string s must be separated by COMMA characters and enclosed by LEFT PARENTHESIS and RIGHT PARENTHESIS characters. See SQL Fundamentals.
- On Teradata Database systems running on SLES 10, account strings include a character that defines the default priority level for use of system resources by sessions that run under the account.
- On Teradata Database systems running on SLES 11, the priority character can be used to indicate a Viewpoint Workload Manager access level associated with the account, but the character does not in itself control the default priority.
- Accounts do not exist independently in the database; they only exist as specified in user, database, and profile definitions. You can specify the same account string in multiple object definitions, if needed.
- The first account string you specify becomes the default account for the user, but you can specify multiple accounts if needed.