databricks Platform · Updated Jun 15, 2026

Unity Catalog Managed Tables

Configure the recovery period for dropped managed tables.

Public Preview Open docs ↗release note ↗

What it does

This update allows users to configure the recovery period for dropped Unity Catalog managed tables, enabling a range from 0 hours (immediate purge) to 30 days. By default, the recovery period is set to 7 days, during which users can recover dropped tables using the UNDROP TABLE command. This feature can be configured at both the catalog and schema levels, with schema-level settings taking precedence.

Why it matters

Configuring the recovery period enhances data governance by providing flexibility in data retention policies, allowing organizations to balance between data recovery needs and cloud storage costs. This is particularly beneficial for businesses that frequently create and drop tables, as it can lead to significant cost savings while ensuring critical data is protected against accidental deletions.

Key capabilities

Configurable Recovery Period

Set the recovery period for dropped tables between 0 to 30 days.

Immediate Purge Option

Option to disable recovery by setting the period to 0 hours.

Schema-Level Configuration

Recovery settings can be applied at both catalog and schema levels.

Accidental Drop Protection

Provides a safeguard against accidental deletions of critical data.

Prerequisites

Databricks Runtime 17.3 or above

Manage privilege or ownership on the catalog or schema

Recommended use cases

Organizations needing flexible data retention policiesTeams frequently creating and dropping tables for testing or developmentData governance frameworks requiring protection against accidental data loss

Limitations · remember

!Only applies to tables dropped after the configuration is set

!Does not affect tables that were already dropped

Architecture

Unity Catalog → Managed Tables → Data Governance → Cloud Storage

Get started

Access Unity Catalog

Navigate to the Unity Catalog in your Databricks workspace.

Select Catalog or Schema

Choose the catalog or schema for which you want to configure the recovery period.

Set Recovery Period

Configure the recovery period to your desired duration (0-30 days).

Save Configuration

Apply and save the changes to enforce the new recovery settings.

Verify Settings

Check the configuration to ensure it reflects the desired recovery period.

Key takeaway

The ability to configure the recovery period for dropped managed tables enhances data governance and cost management in Databricks.

2026-06-15-configure-the-recovery-period-for-dropped-managed-tables-public-preview Generated by the Databricks Updates Agent · browse all updates