On this page
PURGE ENVIRONMENT
Permanently deletes an inactive Environment that no connection uses; DEL ENVIRONMENT makes it inactive first.
Syntax
PURGE ENVIRONMENT <id>
Arguments
| Argument | Required | Values | Default |
|---|---|---|---|
<id> | Yes | The ID of an inactive Environment that no connection, active or inactive, uses (case ignored) | None |
Examples
DEL ENVIRONMENT UAT;
PURGE ENVIRONMENT UAT;
Details
Permanently deletes an inactive Environment from the CDF. DEL ENVIRONMENT makes an Environment inactive (it can be reactivated); PURGE ENVIRONMENT then removes it for good, as the Delete permanently button of the Environments tab of CONFIG does, with the same rules.
Refused for an active Environment, for $CDF and for the built-in LOCAL (BroadSQL creates it again at once), and while a connection, active or inactive, still uses the Environment (the refusal names them). The ID is matched ignoring case, as DEL ENVIRONMENT matches it. The command asks Permanently delete the Environment '<id>'? This cannot be undone [y/n]?; only y or yes purges, and any other answer changes nothing. No connection is needed: the command works at BroadSQL>.
Related
- DEL ENVIRONMENT, to make it inactive first
- SHOW ALL ENVIRONMENTS
- PURGE CONNECTION
Last modified in release 5.6.0.
Found something wrong or unclear on this page? Tell us, with the page address.