16.20 - GRANT (Monitor Form) - Teradata Vantage NewSQL Engine

Teradata Vantageā„¢ SQL Data Control Language

prodname
Teradata Database
Teradata Vantage NewSQL Engine
vrm_release
16.20
created_date
March 2019
category
Programming Reference
featnum
B035-1149-162K

Purpose

Grants system-wide performance monitoring privileges.

Required Privileges

You must have MONITOR privileges to use the monitor form of GRANT.

These privileges should be granted only to those users who are cleared to monitor all applications on all sessions.

There is no lower level of MONITOR privilege: its scope is always global. For example, the database administrator cannot grant user Addams the ability to do session-level monitoring of her applications only. Instead, the DBA would have to grant Addams the permission to do session-level monitoring of all applications by all sessions.

To determine who is currently using the MONITOR partition, issue the following query:

     SELECT UserName, IFPNo
     FROM DBC.SessionInfoV
     WHERE partition = 'MONITOR';

The GRANT statement is used only to assign specific privileges.

To transfer ownership of a database or user, see GIVE.

Syntax



Syntax Elements

MONITOR PRIVILEGES
the named recipients are to receive all MONITOR-related privileges. MONITOR PRIVILEGES does not permit the user to grant the indicated privilege to others without the WITH GRANT OPTION being specified.
MONITOR BUT NOT
the named recipients are to receive all of the grantable privileges except those specified after BUT NOT. If the ability to grant these privileges is to be included, the WITH GRANT OPTION must be specified explicitly.
monitor_privilege
a valid monitoring privilege.
See Monitor Privileges for a list of the valid monitoring privileges.
ALL
to grant the specified object privilege set to the named database or user and to every database or user owned by that database or user now and in the future.
user_name
the name of a user or database to be granted the specified MONITOR privileges. You can specify up to 25 names.
user_name must be the identifier of a user already defined to the system.
PUBLIC
that the privileges are to be inherited by all existing and future Teradata Database users.
WITH GRANT OPTION
that the grantee receives privileges WITH GRANT OPTION. If this option is not specified, the grantee receives the privilege set without the grant option.