SQL/MX 2.x Installation and Management Guide (G06.24+, H06.03+)

Adding, Altering, and Dropping SQL/MX Database
Objects
HP NonStop SQL/MX Installation and Management Guide—523723-004
9-28
Authorization Requirements for Dropping Database
Objects
Authorization Requirements for Dropping Database Objects
Table 9-6 describes the authorization requirement for each drop operation.
Table 9-6. Authorization Requirements for Dropping Database Objects
Operation Authorization Requirements
Dropping Catalogs
Any user can drop any empty catalog visible on the local node. (All
metadata tables for the catalog must be accessible at the time DROP
CATALOG executes.) No user can drop a non empty catalog,
however, even if the catalog contains only empty schemas.
Dropping Columns
To drop a column with a sequence of SQL/MX statements, you must
own its schema or be the super ID.
Dropping
Constraints
To drop a constraint with the ALTER TABLE DROP CONSTRAINT
statement, you must own its schema or be the super ID. You must
also have access to all partitions of the table itself. (ALTER TABLE
works only on user-created tables. You cannot use it to modify a
metadata table even if you are the owner of the metadata tables or a
super ID.)
Dropping Indexes
To drop an index with the DROP INDEX statement, either you must
be the super ID, or you must own the schema that contains the index,
have ALL privileges on the table, and have access to all partitions of
the index and the underlying table.
Dropping Partitions
To drop a partition with the MODIFY utility, you must be the owner of
its schema or the super ID.
To drop only the data in a partition with the PURGEDATA utility,
either you must be the super ID, or you must own the schema and
have ALL privileges on the table (DELETE, INSERT, SELECT, and
UPDATE).
Dropping Schemas
To drop a schema with the DROP SCHEMA statement, you must
own the schema or be the super ID. You must also have remote
passwords for both the node where the catalog of the schema has
been registered, and for any nodes to which the schema has been
replicated.
Dropping SQL/MP
Aliases
To drop an SQL/MP alias with the DROP SQLMP ALIAS statement,
you must be the owner of the schema in which the alias resides or be
the super ID.
Dropping SPJs
To drop an SPJ with the DROP PROCEDURE statement, you must
own the SPJ or be the super ID. For more information, see the
SQL/MX Guide to Stored Procedures in Java.
Dropping Tables
To drop a table with the DROP TABLE statement, you must own its
schema or be the super ID.
Dropping Triggers
To drop a trigger with the DROP TRIGGER statement, you must own
its schema or be the super ID.
Dropping Views
To drop a view with the DROP VIEW statement, you must own the
schema that contains the view or be the super ID.