Removes the specified role from the system.
DROP ROLE [ IF EXISTS ] <name>
Copy
Parameters¶name
Specifies the identifier for the role to drop. If the identifier contains spaces or special characters, the entire string must be enclosed in double quotes. Identifiers enclosed in double quotes are also case-sensitive.
Dropped roles cannot be recovered; they must be recreated.
The current primary role cannot be dropped. An attempt to drop this role returns an error. For example:
CREATE ROLE bobr_primary; GRANT ROLE bobr_primary to USER bobr; USE ROLE bobr_primary; DROP ROLE bobr_primary;
Copy
SQL execution error: Cannot drop role BOBR_PRIMARY as it is the current primary role.
For more information, see Active roles and Authorization through primary role and secondary roles.
A role cannot be dropped if it has the OWNERSHIP privilege on a shared database. Use the GRANT OWNERSHIP command to transfer the OWNERSHIP privilege on the shared database first, and then drop the role.
Ownership of any objects owned by the dropped role is transferred to the role that executes the DROP ROLE command. To transfer ownership of each of these objects to a different role, use GRANT OWNERSHIP … COPY CURRENT GRANTS.
If a role has a future privilege as a grantor or grantee, the role can only be dropped by a user with a role that has the MANAGE GRANTS privilege.
All current and future grants that name the role as either the grantor or the grantee are revoked when the role is dropped.
Query the GRANTS_TO_ROLES Account Usage view to retrieve the privilege grants that name a specified role as the grantor or grantee:
SELECT *
FROM SNOWFLAKE.ACCOUNT_USAGE.GRANTS_TO_ROLES
WHERE grantee_name = UPPER('<role_name>') OR granted_by = UPPER('<role_name>');
Copy
The following example retrieves the grants where myrole is the grantor or grantee:
SELECT *
FROM SNOWFLAKE.ACCOUNT_USAGE.GRANTS_TO_ROLES
WHERE grantee_name = UPPER('myrole') OR granted_by = UPPER('myrole');
Copy
If a role is a grantor of roles to users, dropping the role revokes these grants automatically.
Revoking grants happens as the DROP ROLE command executes. If there are thousands or millions of grants to revoke, the DROP ROLE command might time out. It is safe to rerun the command to continue execution where the previous invocation stopped.
When the IF EXISTS clause is specified and the target object doesn’t exist, the command completes successfully without returning an error.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4