Access Database User Needs | VantageCloud Lake - Assessing Database User Needs - 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
Assess database user needs and develop a user management strategy before you begin running user management setup tasks.
  1. Create a list of all users who require access to Vantage and identify each one according to user type. Minimize the number of user types to simplify user management.
  2. Examine user space requirements:
    • Users who create or own databases, tables and other space-consuming objects require permanent storage space (perm space).
    • Users who run SQL queries, macros, or stored procedures require spool space to contain the required temporary database structures. The spool specification in a profile limits the amount of available space a profile member can use.
  3. Define requirements for one or more account strings. Each profile can include one or more accounts. Each account can specify:
    • Request priority. This classification is in effect only when TASM or TIWM classification processes cannot match the request to a user-defined workload.
    • A four-character account identifier based on department, group, or function.
    • A date and time stamp
    • Define the user default database, that is, the database where the user most often works.
  4. 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.
  5. Identify groups of users with common database privilege requirements and create roles to define the privileges for each group. Consolidate minor differences in access requirement, where possible, to minimize the number of roles.
  6. You may need to assign specialized privileges directly to individual users.