DROP
Statement
Removes objects from the database.
DROP { DBSPACE <dbspace-name> | { DATATYPE [ IF EXISTS ] | DOMAIN } <datatype-name> | EVENT [ IF EXISTS ] <event-name> | INDEX [ IF EXISTS ] [ [ <owner>].<table-name>.]<index-name> | MESSAGE <message-number> | TABLE [ IF EXISTS ] [ <owner>.]<table-name> | VIEW [ IF EXISTS ] [ <owner>.]<view-name> | MATERIALIZED VIEW [ IF EXISTS ] [ <owner>.]<view-name> | PROCEDURE [ IF EXISTS ] [ <owner>.]<procedure-name> | FUNCTION [ IF EXISTS ] [ <owner>.]<function-name> }
- DROP DBSPACE is prevented whenever the statement affects a table that is currently being used by another connection.
- use if you do not want an error returned when the DROP statement attempts to remove a database object that does not exist.
- DROP INDEX deletes any explicitly created index. It deletes an
implicitly created index only if there are no unique or foreign-key
constraints or associated primary key.
DROP INDEX is prevented whenever the statement affects a table that is currently being used by another connection.
For a nonunique HG index, DROP INDEX fails if an associated unenforced foreign key exists.Caution Do not delete views owned by the DBO user. Deleting such views or changing them into tables might cause problems.
- DROP TABLE is prevented whenever the statement affects a table
that is currently being used by another connection or if the primary table
has foreign-key constraints associated with it, including unenforced
foreign-key constraints. It is also prevented if the table has an IDENTITY
column and IDENTITY_INSERT is set to that table. To drop the table you must
clear IDENTITY_INSERT, that is, set IDENTITY_INSERT to ' ' (an empty
string), or set to another table name.
A foreign key can have either a nonunique single or a multicolumn HG index. A primary key may have unique single or multicolumn HG indexes. You cannot drop the HG index implicitly created for an existing foreign key, primary key, and unique constraint.
The four initial dbspaces are SYSTEM, IQ_SYSTEM_MAIN, IQ_SYSTEM_TEMP, and IQ_SYSTEM_MSG. You cannot drop these initial dbspaces, but you may drop dbspaces from the IQ main store or catalog store, which may contain multiple dbspaces, as long as at least one dbspace remains with readwrite mode.
You must drop tables in the dbspace before you can drop the dbspace. An error is returned if the dbspace still contains user data; other structures are automatically relocated when the dbspace is dropped. You can drop a dbspace only after you make it read-only.
Note A dbspace may contain data at any point after it is used by a command, thereby preventing a DROP DBSPACE on it.In a multiplex, dropping of RLV-enabled tables is only allowed on the coordinator.
- DROP PROCEDURE is prevented when the procedure is in use by another connection.
- DROP DATATYPE is prevented if the data type is used in a table. You must change data types on all columns defined on the user-defined data type to drop the data type. It is recommended that you use DROP DOMAIN rather than DROP DATATYPE, as DROP DOMAIN is the syntax used in the ANSI/ISO SQL3 draft.
- drop the Departments table from the database:
DROP TABLE Departments
- drop the emp_dept view from the database:
DROP VIEW emp_dept
- drop the myDAS main cache from the simplex or
multiplex node you are connected to:
DROP DBSPACE myDAS
DROP removes the definition of the indicated database structure. If the structure is a dbspace, then all tables with any data in that dbspace must be dropped or relocated prior to dropping the dbspace; other structures are automatically relocated. If the structure is a table, all data in the table is automatically deleted as part of the dropping process. Also, all indexes and keys for the table are dropped by DROP TABLE.
- Automatic commit. Clears the Data window in dbisql. DROP TABLE and DROP INDEX close all cursors for the current connection.
- Local temporary tables are an exception; no commit is performed when one is dropped.
- SQL—ISO/ANSI SQL compliant.
- SAP Database products—Supported by SAP ASE.