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

Adding, Altering, and Dropping SQL/MX Database
Objects
HP NonStop SQL/MX Installation and Management Guide—544536-007
9-34
Dropping SPJs
Steps for Dropping an SQL/MP Alias
1. Start an MXCI session. Enter a LOG command to initiate a log file for statements
and commands entered in this session. Keep the log for your records.
2. Determine the name of the SQLMP alias that you wish to drop.
3. Use the DISPLAY USE OF command to identify which user modules are
associated with this object. See the similarity check criteria in the SQL/MX
Programming Manual for C and COBOL to determine if your changes are likely to
cause similarly check to fail and force automatic recompilation. If they will, you
should SQL compile these modules after making the changes to avoid expensive
automatic recompilations at run time. SQL applications that are running while you
make these changes will still undergo automatic recompilation.
For information about explicit and automatic recompilation, see the SQL/MX
Programming Manual for C and COBOL. For information about using DISPLAY
USE OF, see Checking Module Dependencies with DISPLAY USE OF on
page 11-19 and the SQL/MX Reference Manual.
4. Enter the DROP SQLMP ALIAS statement.
5. Revise the application source code as needed to reflect your changes to the
database. Process and compile the updated source file. For more information, see
the SQL/MX Programming Manual for C and COBOL.
For more information and examples of dropping SQL/MP aliases, see the SQL/MX
Reference Manual.
Dropping SPJs
For information about and examples of dropping SPJs, see the SQL/MX Guide to
Stored Procedures in Java.
Dropping SQL/MX Tables
To remove a table and its dependent objects from the database, use the DROP TABLE
statement. Use the PURGEDATA utility to remove only the data from a table and its
dependent objects and leave the objects intact.
For more information, see the SQL/MX Reference Manual.
Dropping SQL/MX Tables and Their Data
To drop a table and its data, use the DROP TABLE statement. Dropping a base table
with dependencies is essentially dropping each of the dependent objects (indexes,
constraints) separately. SQL drops all the dependencies automatically.
If the table contains references to another object (for example, an RI constraint), the
drop operation fails if RESTRICT is specified. The drop operation should succeed if
you use the CASCADE option to drop these dependent objects.