Delete Table Release For Free

Dropping a table removes the table definition from the data dictionary. All rows of the table are no longer accessible. All indexes and triggers associated with a table are dropped. All views and PL/SQL program units dependent on a dropped table remain, yet become invalid (not usable).

Specify PURGE if you want to drop the table and release the space associated with it in a single step. If you specify PURGE , then the database does not place the table and its dependent objects into the recycle bin.

When a table is dropped, rules or defaults on the table lose their binding, and any constraints or triggers associated with the table are automatically dropped. If you re-create a table, you must rebind the appropriate rules and defaults, re-create any triggers, and add all required constraints.

If you want to permanently drop an index from the recycle bin, you can do so using: SQL> PURGE INDEX index-name; This will remove the index only, leaving the copy of the table in the recycle bin. Sometimes it might be useful to purge at a higher level.

Purpose. Use the PURGE statement to remove a table or index from your recycle bin and release all of the space associated with the object, or to remove the entire recycle bin, or to remove part of all of a dropped tablespace from the recycle bin.

Totally safe in any level. As you surely know, in recycle bin are dropped objects, those objects are not referenced by any other object in the database. That's why there is not any risk if you purge the recycle bin.

Purging is the process of freeing up space in the database or of deleting obsolete data that is not required by the system. The purge process can be based on the age of the data or the type of data.