SQL/MX 2.x Reference Manual (H06.04+)

SQL/MX Statements
HP NonStop SQL/MX Reference Manual540440-003
2-121
Considerations for DROP PROCEDURE
Considerations for DROP PROCEDURE
Required Privileges
To issue a DROP PROCEDURE statement, you must own the SPJ or be the super ID.
Example of DROP PROCEDURE
Drop an SPJ named ADJUSTSALARY from NonStop SQL/MX:
DROP PROCEDURE samdbcat.persnl.adjustsalary;
DROP SCHEMA Statement
Considerations for DROP SCHEMA
Examples of DROP SCHEMA
The DROP SCHEMA statement deletes an SQL/MX schema. See Schemas on
page 6-101.
Syntax Description of DROP SCHEMA
schema
is the name of the schema to drop.
If you specify RESTRICT, an error is reported if the specified schema is not empty.
If you specify CASCADE, objects in the specified schema in addition to the
schema itself are dropped. The default is RESTRICT.
Considerations for DROP SCHEMA
Reserved Schemas
Schema names of the form DEFINITION_SCHEMA_VERSION_ are reserved in all
catalogs for system metadata.
Schema names SYSTEM_SCHEMA and SYSTEM_DEFAULTS_SCHEMA are
reserved, but only in catalogs with a name of the form NONSTOP_SQLMX_. These
schema names are not reserved when used in a user-created catalog. Schemas
named MXCS_SCHEMA in all catalogs are reserved for use by MXCS.
You cannot drop any of these reserved schemas or the objects contained in them.
DROP SCHEMA schema [CASCADE | RESTRICT]