User Planning - Teradata Vantage

Teradata® VantageCloud Lake

Deployment
VantageCloud
Edition
Lake
Product
Teradata Vantage
Published
January 2023
Language
English (United States)
Last Update
2024-04-03
dita:mapPath
phg1621910019905.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
phg1621910019905

Before beginning the user provisioning tasks, determine database user needs and develop a user management strategy.

Resource requirements:
  • Who needs access to VantageCloud Lake? Create a list of all users, and identify each one according to user type. Minimize the number of user types to simplify user management.
  • Which type of users need access to compute clusters? What is the appropriate compute group for each user type?

    See VantageCloud Lake Architecture.

  • What type of priority do the user queries get? Priority levels are called workloads in VantageCloud Lake. The workloads are set by default. You can override the default using a user’s account string assignment, if you use account strings. The following workloads can be set:
    Workload Name Priority Account String
    Tactical-WD Tactical $TA
    T-WD Timeshare Top $R
    H-WD Timeshare High $H
    M-WD Timeshare Medium $M
    L-WD Timeshare Low $L
    WD-Default Timeshare Medium User does not have account string
    WD-Default is a viable option and is a good starting point to use without account string assignments. It runs all queries at the default medium priority.
    Do not use Account String Expansion (ASE) variables in VantageCloud Lake.
  • What additional privileges do users get? Review the database objects (such as views, tables, macros, functions, and procedures) that users or user groups must access to do their job. Define database privileges at the highest level appropriate for the user. For example, if a user requires the same privileges on all views in a database, assign privileges at the database level.

    See User Privileges for commonly-assigned privileges for users.

System requirements:
  • Do your security policies allow generic passwords for all users initial login? If not, is there a policy to define initial logins? Is the system set up to prompt new users to choose their own passwords?

    See Creating Temporary Passwords for First Login.

  • What types of user profiles are needed? Profiles define resource parameters for groups of users with similar needs instead of defining the resources for each individual user.

    See Creating User Profiles.

  • Are there roles that can be used for groups of users? Roles give a set of privileges to users with common privilege requirements. For minor privilege differences, you can assign additional privileges directly to individual users.

    See Using Roles to Manage User Privileges.

  • What type of space do users need? There is permanent and spool space available based on user needs.
    • Assign permanent storage space to users who create or own databases, tables and other space-consuming objects.
    • Assign spool space to users who run SQL queries, macros, or stored procedures. The spool specification in a profile limits the amount of available space a profile member can use.
    Spool space requirements in a profile depend on the activities of member users on the Primary Cluster. Begin by specifying spool space in bytes, according to the following percentages of the total perm space allocation:
    • General users: 5%
    • Update users: 10%
    • Batch users: 10%
    • Assistant administrative users: 10%
    • Business analysts, data analysts, and database programmers: 10%

    See Sizing Spool Space.