Deletes definitions from a database or deletes an entire schema.

Additional information available:

DATABASECOLLATING_SEQUENCECONSTRAINTDOMAIN
INDEXPATHNAMESCHEMASTORAGE_MAPTABLETRIGGER
VIEW

 DROP DATABASE is supported only for upward compatibility.  For
 information on dropping databases see the Help topic on DROP SCHEMA.

 DROP COLLATING SEQUENCE ──> sequence-name;

Additional information available:

More Information

 Deletes the named collating sequence.

 You cannot delete a collating sequence if it is used by the schema or
 by any domain in the schema.

 Deletes the following types of constraints:

  o  Constraints defined by the RDO DEFINE CONSTRAINT statement

  o  Constraints defined with versions of the SQL interface provided
     prior to version 3.1 of Rdb/VMS


 DROP CONSTRAINT ──> constraint-name ────> typebox (;)

Additional information available:

constraint-nameMore Information

 The name of the constraint you want to delete.

 The following types of constraints cannot be deleted using DROP
 CONSTRAINT:

 1.  Table-specific constraints defined with the CREATE TABLE
     statement of the SQL interface provided with Version 3.1 of
     Rdb/VMS.

     Use the DROP CONSTRAINT clause of the SQL ALTER TABLE statement
     to delete this type of constraint.

 2.  Relation-specific constraints defined using the RDO DEFINE
     RELATION statement provided with Version 3.1 of Rdb/VMS.

     Use the DELETE CONSTRAINT clause of the RDO CHANGE RELATION
     statement to delete this type of constraint.

 DROP DOMAIN ──> domain-name ;

Additional information available:

More Information

 Deletes a domain definition.  When the DROP DOMAIN statement
 executes, VAX SQL drops the domain definition from the physical
 database.  If you declared the schema using the PATHNAME qualifier,
 VAX SQL also drops the domain definition from the data dictionary.

 You can drop any named domain once you have declared the schema that
 includes the domain.  However, you cannot drop a domain that is
 referred to in a column definition in a table.  If you want to drop a
 domain that is referred to in a column definition, you must first
 drop the column definition using the ALTER TABLE statement.  If the
 column definition is used in a constraint or index definition, you
 must first drop the constraint or index definition, then drop the
 column definition.

 DROP INDEX index-name ────> typebox (;)

Additional information available:

More Informationindex name

 DROP INDEX deletes the specified index definition.  When the DROP
 INDEX statement executes, SQL deletes the index definition from the
 schema.  If you declare the schema using the PATHNAME qualifier, SQL
 also deletes the index definition from the data dictionary.

 You cannot delete an index definition unless you have declared the
 schema that includes the index.  You also cannot delete an index when
 there are other users who have declared the same schema.  You must
 execute this statement in a READ WRITE transaction.

 The name of the index definition you want to delete.

 DROP PATHNAME  ──>  path-name──> typebox (;)

Additional information available:

More Information

 Deletes the data dictionary definitions specified by the pathname
 argument.  It does not delete the physical database files.

 DROP SCHEMA ──┬─> typebox (A)typebox (U)typebox (T)typebox (H)typebox (O)typebox (R)typebox (I)typebox (Z)typebox (A)typebox (T)typebox (I)typebox (O)typebox (N) auth-id ─┬─> typebox (;)
               ├─> 
F
I
L
E
N
A
M
E file-spec ────┤
               └─> 
P
A
T
H
N
A
M
E path-name ────┘

Additional information available:

More Informationauth idfile specpath name

 DROP SCHEMA deletes a schema.  When this statement executes, SQL
 deletes all the database files associated with the schema.  If you
 specify a data dictionary path name in the DROP SCHEMA statement, SQL
 also deletes the data dictionary directory that contains the schema
 definitions.

                                 NOTE

         Use the DROP SCHEMA statement with care.  You cannot
         use ROLLBACK to cancel a DROP SCHEMA statement.  When
         you use this statement, SQL deletes all database
         files, which includes all data and all definitions.

 The authorization identifier of an already-declared schema.

 A full or partial file specification that names the database files.
 If you use a partial file specification, SQL uses the standard VMS
 defaults.  If you use a file specification, DROP SCHEMA only deletes
 database files, whether or not there is also a data dictionary
 directory containing schema definitions.

 A full or relative data dictionary path name for the dictionary
 directory where the schema definitions are stored.  Use a path name
 instead of a file specification to delete the data dictionary
 definitions for the schema from the data dictionary along with the
 database files.

 DROP STORAGE MAP ──> map-name ──> typebox (;)

Additional information available:

More Information

 Deletes the specified storage map definition.

 Do not use the DROP STORAGE MAP and CREATE STORAGE MAP statements to
 change a storage map.  Use the ALTER STORAGE MAP statement instead.

 You cannot delete a storage map if you have declared the schema that
 includes the storage map.

 Other users are allowed to be attached to the schema when you issue
 the DROP STORAGE MAP statement.

 You cannot drop a storage map that refers to a table that has data in
 it.  If you attempt to do so, you will receive an error message.
 However, you can drop the table once the necessary views and
 constraints have been dropped, and the underlying storage map will be
 dropped with the table and its data.

 DROP TABLE table-name ─┬────────────┬──> typebox (;)
                        ├─> 
C
A
S
C
A
D
E ─┤
                        └─> 
R
E
S
T
R
I
C
T ┘

Additional information available:

More Informationtable name

 DROP TABLE deletes the table definition specified.  When the DROP
 TABLE statement executes, SQL deletes the table definition and the
 data stored in that table from the database.  If you use the PATHNAME
 qualifier when you declare the database, DROP TABLE also deletes the
 table definition from the data dictionary.

 You must specify a keyword that indicates whether you desire
 cascading deletes.  If you want SQL to delete all items that refer to
 the table, and then delete the table, use DROP TABLE CASCADE.  If you
 want SQL to drop only the table, use DROP TABLE RESTRICT.  If there
 are views, constraints, triggers, or indexes that refer to the table,
 the drop fails.

 You must execute the DROP TABLE statement in a READ WRITE
 transaction.  If you issue this statement when there is no active
 transaction, SQL starts a transaction with characteristics specified
 in the most recent DECLARE TRANSACTION statement.

 You cannot delete a table definition unless you have declared the
 schema that includes the table.  Also, you cannot delete a table when
 there are other active transactions involving the table.  That is,
 you must have exclusive access to the table.

 If a view definition refers to a table you want to drop, you must
 drop that view definition before you drop the table.

 If a constraint in the schema references a table, you cannot drop
 that table until you drop the constraint that references the table.

 The name of the table definition you want to delete.

 DROP TRIGGER  ─┬─ trigger-name  ──┬──> typebox (;)
                └──────  , <───────┘

Additional information available:

More Informationtrigger name

 DROP TRIGGER deletes one or more trigger definitions from the
 physical database, and if the schema has been declared with PATHNAME,
 from the data dictionary.

 To drop a trigger, you must have DELETE access to the table for which
 the trigger is defined.

 You must execute this statement in a read/write transaction.  If you
 issue this statement when there is no active transaction, SQL starts
 a read/write transaction implicitly.

 Other users are allowed to be attached to the database when you issue
 the DROP TRIGGER statement.

 The name of the trigger you want to delete.

 DROP VIEW view-name ─┬────────────┬──> typebox (;)
                      ├─> 
C
A
S
C
A
D
E ─┤
                      └─> 
R
E
S
T
R
I
C
T ┘

 DROP VIEW deletes the specified view definition.  When the DROP VIEW
 statement executes, SQL deletes the view definition from the physical
 database.  If you declare the schema using the PATHNAME qualifier,
 SQL also deletes the view definition from the data dictionary.

 You can delete a view definition even when there are active users.
 Deleting a view definition does not affect active users until you
 commit your transaction, and they exit their session and declare the
 database again.

 You must specify a keyword that indicates whether you desire
 cascading deletes.  If you want SQL to delete all items that refer to
 the view, and then delete the view, use DROP VIEW CASCADE.  If you
 want SQL to drop only the view, use DROP VIEW RESTRICT.  If there are
 other views that refer to the view, the drop fails.

 You must execute this statement in a READ WRITE transaction.  If you
 issue this statement when there is no active transaction, SQL starts
 a transaction with characteristics specified in the most recent
 DECLARE TRANSACTION statement.

Additional information available:

view name

 The name of the view definition you want to delete.