SQL/MX 3.2.1 Management Manual (H06.26+, J06.15+)

Table 12 Dropping Objects From an SQL/MX Database
Statement, Command or UtilityOperationObject
DROP CATALOG statementDropCatalog
ALTER TABLE DROP CONSTRAINT statementDropConstraint
DROP INDEX statementDrop data, file and definitionIndex
MODIFY utilityDrop data, file and definitionPartition
PURGEDATA utilityDrop data only
DROP SCHEMA statementDrop schemaSchema
DROP SEQUENCE statementDrop SequenceSequence Generator
DROP SQLMP ALIAS statementDrop the mapSQL/MP alias
DROP PROCEDURE statementDrop procedureStored procedures in Java (SPJ)
DROP TABLE statementDrop data, files and definitionTable
PURGEDATA utilityDrop data only
DROP TRIGGER statementDrop triggerTrigger
DROP VIEW statementDrop viewView
For more information, see the SQL/MX Reference Manual. For more information about application
programs, see “Managing Database Applications” (page 212).
Authorization Requirements for Dropping Database Objects
Table 13 (page 169) describes the authorization requirement for each drop operation.
In a distributed environment, all DROP operations require the executing user-id to have remote
password set up between the local system and any remote system that is affected by the operation.
A remote system is affected by a DROP operation if:
• metadata for the target object reside on that system
• locations for the target object reside on that system
Table 13 Authorization Requirements for Dropping Database Objects
Authorization RequirementsOperation
To drop a catalog, you must be the owner of the catalog, or be the super ID. In a
distributed environment, you must have remote password set up for all nodes where
the target catalog is visible.
“Dropping Catalogs” (page 170)
To drop a column with a sequence of SQL/MX statements, you must own its schema
or be the super ID.
“Dropping Columns from an
SQL/MX Table” (page 170)
To drop a constraint with the ALTER TABLE DROP CONSTRAINT statement, you must
be the owner of the table, or own its schema, or be the super ID. You must also have
access to all partitions of the table itself.
“Dropping Constraints”
(page 171)
To drop an index with the DROP INDEX statement, you must be the owner of the
index, or own its schema, or be the super ID. You must also have access to all
partitions of the index and the underlying table.
“Dropping SQL/MX Indexes”
(page 172)
To drop a partition with the MODIFY utility, you must be the owner of the affected
table, or own its schema or be the super ID.
nl
“Dropping Partitions for
SQL/MX Tables and Indexes”
(page 172)
To drop only the data in a partition with the PURGEDATA utility, you must be the
owner of the table, or be the super ID, or you must have ALL privileges on the table
(DELETE, INSERT, SELECT, and UPDATE).
Dropping Objects From an SQL/MX Database 169