ADMIN Role (db)

ADMIN is a superuser with full privileges to monitor MC-managed database activity and messages. Other database privileges (such as stop or drop the database) are governed by the user account on the Vertica database that this ADMIN (db) user is mapped to. ADMIN is the most permissive role and is a superset of privileges granted to the Associate Role (Database), IT, and USER roles.

The ADMIN user has the following database privileges by default:

  • View the database Overview page
  • View and delete database messages
  • Mark messages read or unread
  • Start the database
  • View the Manage page

  • View node details

  • Start or stop a node
  • View database settings
  • View the following database Activity page charts:

    • Queries

    • Internal Sessions

    • User Sessions

    • System Bottlenecks

    • User Query Phases

The following database operations depend on the database user's role that you mapped this ADMIN user to:

  • Install or audit a license
  • Rebalance, stop, or drop databases
  • Add, replace, or remove nodes
  • Manage database settings
  • View Database Designer

  • View additional information on the database Activity page:

    • Detailed information in the Queries chart Detail page
    • Table Treemap chart
    • Query Monitoring chart
    • Resource Pools Monitoring chart

Database access granted through Management Console never overrides roles granted on a specific Vertica database.

About the ADMIN (MC configuration) Role

There is also an MC configuration administrator role that defines what the user can change on the MC itself. The two ADMIN roles are not the same. Unlike the MC configuration role of ADMIN, which can manage all MC users and all databases imported into the UI, the MC database ADMIN role has privileges only on the databases you map this user to. The following table summarizes the primary difference between them. See ADMIN Role (mc) for additional details.

MC database ADMIN role MC configuration ADMIN role

Perform database-specific activities, such as stop and start the database, and monitor query and user activity and resources. Other database operations depend on that user's privileges on the specific database. This ADMIN role cannot configure MC.

Perform all administrative operations on the MC itself, including restarting the MC process. Privileges extend to monitoring all databases created and imported by MC. Anything database-related beyond that scope depends on the user's privileges granted on the database through GRANT statements.