REVOKE statement (authorities and groups) (deprecated)

REVOKE privilege, ... FROM userid, ...

permission : 
BACKUP 
| CONNECT 
| CREATE ON dbspace
| DBA
| GROUP 
| INTEGRATED LOGIN
| KERBEROS LOGIN 
| MEMBERSHIP IN GROUP userid, ... 
| PROFILE
| READCLIENTFILE 
| READFILE 
| [ RESOURCE | ALL ]
| VALIDATE
| WRITECLIENTFILE

authority

Note

When you revoke authorities using the old deprecated REVOKE syntax, the database server converts the authority to its equivalent compatibility roles.
- BACKUP authority Converted to revoking the SYS_AUTH_BACKUP_ROLE compatibility role.
- DBA authority Converted to revoking the SYS_AUTH_DBA_ROLE, SYS_AUTH_SA_ROLE, and SYS_AUTH_SSO_ROLE compatibility roles.
- PROFILE authority Converted to revoking the SYS_AUTH_PROFILE_ROLE compatibility role.
- READ CLIENT FILE privilege Converted to revoking the SYS_AUTH_READCLIENTFILE_ROLE compatibility role.
- READ FILE privilege Converted to revoking the SYS_AUTH_READFILE_ROLE compatibility role.
- RESOURCE or ALL authority Converted to revoking the SYS_AUTH_RESOURCE_ROLE compatibility role.
- VALIDATE authority Converted to revoking the SYS_AUTH_VALIDATE_ROLE compatibility role.
- WRITECLIENTFILE authority Converted to revoking the SYS_AUTH_WRITECLIENTFILE_ROLE compatibility role.
GROUP clause This converts a user-extended role (group) back to a regular user so they are no longer a group that users can be added to.
MEMBERSHIP IN GROUP clause This revokes membership in a user-extended role (group).

REVOKE GROUP automatically revokes MEMBERSHIP IN GROUP from all members of the group.

When you add a user to a group, the user inherits all the privileges assigned to that group. SQL Anywhere does not allow you to revoke a subset of the privileges that a user inherits as a member of a group because you can only revoke privileges that are explicitly given by a GRANT statement. If you require different privileges for different users, create different groups with the appropriate privileges, or explicitly grant each user the privileges they require.

If you revoke a privilege for a user and they also had WITH GRANT OPTION for that privilege, then everyone who that user granted the privilege to also has their privilege revoked. For example, suppose you granted UserA SELECT...WITH GRANT OPTION privileges on a table and UserA then grants the SELECT privilege on the table to UserB. If you revoke the SELECT privilege from UserA, it is revoked from UserB as well.

You must have administrative rights for the equivalent role you are revoking. For example, if you are revoking the ability to backup databases, and are using the REVOKE BACKUP syntax, you must have administration rights on the SYS_AUTH_BACKUP_ROLE compatibility role.

Changes to the REVOKE statement syntax
To view the new REVOKE statement syntax, see REVOKE statement.
To view the mapping of authorities to compatibility roles, see Compatibility roles.
To determine what roles you have administrative rights for, see Viewing the roles and privileges for a user or role (Sybase Central), or Viewing the roles and privileges for a user or role (SQL).
To review the SQL Anywhere 12.0.1 REVOKE statement syntax, see http://dcx.sybase.com/index.html#1201/en/dbreference/revoke-statement.html.

REVOKE statement (authorities and groups) (deprecated)

Note

Syntax 1 - Revoke authorities

Parameters

Note

Remarks

Privileges

See also