Hi @woodymo,

Dropped Unity Catalog tables remain recoverable with UNDROP for roughly 7 days, and SHOW TABLES DROPPED lists dropped tables that are still within that retention window. This is expected behaviour as per the documentation.

For the actual delete path, the public docs say DROP TABLE deletes tables within 7 to 30 days, and after the recovery window, the underlying data is marked for deletion during regular maintenance operations rather than being purged immediately.

So, based on the current public documentation, there does not appear to be a documented self-serve/public command to immediately purge an already soft-deleted Unity Catalog table or schema. If the metastore quota is still blocking new table creation even after cleanup, the practical next step is to open a Databricks support case and include the metastore ID and the exact QUOTA_EXCEEDED error.

For future workflows, if the pattern is "drop and recreate the same table name," Databricks recommends using CREATE OR REPLACE TABLE instead of DROP TABLE + CREATE TABLE, because drop/recreate can lead to unexpected results in production pipelines and concurrent operations.

Hope this helps.

If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.