The DELETE command deletes the currently selected object or range of objects, including all descendants and antecedents, meaning the delete cascades both up and down through the index structure.
The DELETE command can damage the File System B*Tree such that data can be removed or lost permanently. If used incorrectly, changes might be irreversible.
Prevents Filer from prompting for confirmation before executing the command.
The selected object or range is from the last operation and is saved in the context. Executing SHOWD displays the selected object or range. For more information, see “SHOWDEFAULTS” on page 209.
The delete context can be a row, table, DB, DBD, CI, CID, WAL log record, WDB, WDBD, WCI, WCID, or DEPOT, and ranges thereof. If a WAL object is selected, DELETE cascades throughout the WAL log index structure.
DELETE can apply to one, several or all AMPs, depending on the current scope. The DELETE confirmation scope can span AMPs but is condensed into a single range. For some ranges, DELETE is allowed only when the Teradata Database is down.
If you delete a single DEPOT cylinder, the scope can be on one AMP or all AMPs. If you delete the entire DEPOT, the scope must be on all AMPs. This command is allowed only when the Teradata Database is offline.
If there is a whereclause in the context, then only those rows or WAL log records that satisfy the whereclause are deleted. For more information on the whereclause, see “Specifying a WHERE clause” on page 85.
Only tables and rows can be deleted if running from remote DBW console with multiple vprocs selected.
If the selected object is a CI, then the DELETE command effectively performs the same action as the INIT command. For more information, see “INIT” on page 141.
For example, deleting a CI would remove the CID from the MI and all DBs with DBDs in the CI.