Account String Variables | VantageCloud Lake - Account String Variable - Teradata VantageCloud Lake

Lake - Database Reference
Deployment
VantageCloud
Edition
Lake
Product
Teradata VantageCloud Lake
Release Number
Published
February 2025
ft:locale
en-US
ft:lastEdition
2025-11-21
dita:mapPath
ohi1683672393549.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
ohi1683672393549

You can set the account string in the User record or the Profile record in the Data Dictionary. If you submit a query without an account string specified in the User or Profile record, or if the workload classification in the account string is invalid, that query will run in a workload named WD-Default, which operates at medium priority. This default setting is a viable option in VantageCloud Lake and serves as a good starting point to run all queries at the default medium priority without assigning account strings.

Here is an example of how to assign a user to a priority based on an account string:
MODIFY USER Dashboard_User AS ACCOUNT = '$H';
If you choose to use account strings, avoid using Account String Expansion (ASE) variables in VantageCloud Lake. ASE variables act as placeholders for values such as session number or date, which the system fills in when the query runs. Traditionally, in Teradata platforms, an ampersand (&) designates an ASE variable within an account string. A typical account string using ASE might look like this: '$H00FINR&D&H'. The database automatically replaces these ASE variables with actual values when a user session is active. Commonly used ASE variables include:
  • &D = the date of the request
  • &H = the time of the request

ASE variables have influenced the granularity of CPU and I/O data collected in the DBC.Acctg table. In a Primary Cluster-only system, ASE variables will continue to behave as they do in traditional Teradata platforms. However, DBC.Acctg information will not be available, so you should discontinue using ASE variables in the VantageCloud Lake environment.