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

SQL/MX Statements

HP NonStop SQL/MX Reference Manual—540440-003

2-120

Examples of DROP INDEX

•

This example drops an index:

DROP INDEX myindex;

DROP PROCEDURE Statement

Considerations for DROP PROCEDURE

Example of DROP PROCEDURE

The DROP PROCEDURE removes a stored procedure in Java (SPJ) from

NonStop SQL/MX. To develop, deploy, and manage SPJs in SQL/MX, see the SQL/MX

Guide to Stored Procedures in Java.

procedure-ref

specifies an ANSI logical name of the form:

[[catalog-name.]schema-name.]procedure-name

where each part of the name is a valid SQL identifier with a maximum of 128

characters. For more information, see Identifiers on page 6-52.

If you do not fully qualify the procedure name, NonStop SQL/MX qualifies it

according to the current settings of CATALOG and SCHEMA. If you set the

NAMETYPE attribute to NSK instead of ANSI and you do not fully qualify the

procedure name, NonStop SQL/MX returns an error. For more information on the

CATALOG, SCHEMA, and NAMETYPE attributes, see the System Defaults Table

on page 10-30.

You cannot specify SQL parameters along with the procedure name. Each

procedure name represents a unique SPJ in the database because

NonStop SQL/MX does not support the overloading of procedure names.

RESTRICT

has no effect because NonStop SQL/MX does not record dependencies on the

SPJ in the SQL/MX user metadata (UMD) tables, system metadata, and MXCS

metadata tables. The default is RESTRICT.

DROP PROCEDURE procedure-ref [RESTRICT]

procedure-ref is:

[[catalog-name.]schema-name.]procedure-name