Books
in black and white
Main menu
Share a book About us Home
Books
Biology Business Chemistry Computers Culture Economics Fiction Games Guide History Management Mathematical Medicine Mental Fitnes Physics Psychology Scince Sport Technics
Ads

Teradata RDBMS forUNIX SQL Reference - NCR

NCR Teradata RDBMS forUNIX SQL Reference - NCR, 1997. - 913 p.
Download (direct link): teradataforunix1997.pdf
Previous << 1 .. 172 173 174 175 176 177 < 178 > 179 180 181 182 183 184 .. 241 >> Next

PUBLIC Specifies that the privileges are to be revoked from all currently defined and future users of the Teradata RDBMS. ALL DBC is equivalent to PUBLIC.

Teradata RDBMS for UNIX SQL Reference

8-235
Teradata SQL Syntax Guide

REVOKE Statement (MONITOR)

REVOKE Statement (MONITOR)

The MONITOR form rescinds system-wide performance monitoring privileges.

Syntax

TTO3

lFROM-1

lALL-I

- username -

PUBLIC-

FF07A062

where:

Syntax Element ... Description
GRANT OPTION FOR When GRANT OPTION FOR is specified, then only the grant authority is removed from the specified rights for the specified grantees. REVOKE GRANT OPTION FOR revokes the recipient’s right to grant, but does not revoke the stated privileges themselves.
MONITOR BUT NOT Revokes all of the MONITOR privileges except those specified.

8-236

Teradata RDBMS for UNIX SQL Reference
Teradata SQL Syntax Guide

REVOKE Statement (MONITOR)

Syntax Element ... Description
MONITOR PRIVILEGES Revokes from the specified user all privileges, except MONITOR, that may be granted on the specified object, and that are possessed WITH GRANT OPTION by the user executing the REVOKE. To revoke all of a user’s privileges, including MONITOR, the revoker must execute at least two commands, shown as follows: REVOKE ALL PRIVILEGES ON object from username ; REVOKE MONITOR PRIVILEGES from username ; ALL PRIVILEGES means only all database privileges. If the ALL PRIVILEGES is used, then only the rights possessed with grant authority are revoked from the grantee. MONITOR PRIVILEGES indicates all monitoring privileges. ANSI SQL requires ALL to be followed by PRIVILEGES.

Monitor Privileges List:

ABORTSESSION Aborts any outstanding request or ongoing transaction of one or more Teradata RDBMS sessions and, optionally, logs off the sessions.
MONRESOURCE Gathers information on how each AMP and PE is performing, and each processor’s availability.
MONSESSION Gathers information about logged on sessions and overall system usage on a session-by-session basis.
SETRESRATE Sets the frequency at which processor resource usage data is updated in the Teradata RDBMS.
SETSESSRATE Sets the frequency at which session-level performance data is updated in the Teradata RDBMS. Any combination of privileges can be revoked by a user who has those privileges with GRANT option.

For REVOKE (SQL), the user submitting a REVOKE statement must Privileges Required be the owner of the object, or must have all of the privileges that are

to be revoked, on the object, with GRANT option.

If the object is a view or macro, the submitting user also must have the applicable privileges, WITH GRANT OPTION, on the objects referenced by the view or macro.

For REVOKE (Monitor), the user submitting a REVOKE statement must have all the privileges that are to be revoked with GRANT option.

Teradata RDBMS for UNIX SQL Reference

8-237
Teradata SQL Syntax Guide

REVOKE Statement (MONITOR)

Rules for Using REVOKE

To REVOKE Statement and REVOKE Monitor, Execute Both Statements

ALL PRIVILEGES

Which Privileges Can be Revoked?

Revoking Column Level Rights

It is illegal to specify an ON object clause in a REVOKE MONITOR statement. It is illegal not to specify an ON object clause in any other REVOKE statement. If you violate either one of these restrictions, a failure response will occur.

REVOKE takes effect immediately when the revokee issues his next command.

The SQL and MONITOR forms of REVOKE are separate statements. To revoke all a user’s privileges including MONITOR, the grantor must execute both statements, thus:

REVOKE ALL PRIVILEGES ON <object>

FROM <username> ;

REVOKE MONITOR PRIVILEGES FROM <username> ;

ALL PRIVILEGES means that only all database-related privileges are affected. MONITOR PRIVILEGES indicates that all monitoring privileges are affected.

Ownership privileges cannot be revoked.

If a REVOKE statement removes privileges that were granted at the database or user level, the privileges are dropped for all objects, regardless of when they were created. A REVOKE statement at the object level cannot remove from that object a privilege that was granted at the database or user level.

A REVOKE of the GRANT OPTION for a privilege immediately rescinds the right to grant that privilege. However, it does not affect privileges that have already been granted by the target user to other users.

• If a user receives the same privilege from two or more grantors, any grantor who has the necessary privileges may revoke that privilege from the user, and from other grantees; one who revokes a privilege from another need not be the grantor of that privilege.

• If a privilege that was granted to “ALL name” is revoked from “name,” the privilege is not automatically granted to future users who are owned by “name.”

Revocation of a column level right is only allowed if there is a row in the access rights table for the columns on which the right is to be revoked. This means that if the user has UPDATE or REFERENCES right at the table level, revoking the right on individual columns is not allowed.
Previous << 1 .. 172 173 174 175 176 177 < 178 > 179 180 181 182 183 184 .. 241 >> Next