---
title: "Your data, your storage, your rules: a 2026 guide to storing Unity Catalog managed tables"
description: "Unity Catalog managed tables let you control where your data physically resides while keeping it in cloud storage you own, such as S3, ADLS, or GCS, unlike platforms that store tables in provider-controlled storage. You set managed storage locations at the metastore, catalog, or schema level, with the most specific level winning, and can change where new tables land using ALTER CATALOG or ALTER SCHEMA commands. Managed tables use open formats including Iceberg and Delta, and external engines such as Apache Spark, Flink, and Trino can read and write through Iceberg REST Catalog and Unity Catalog open APIs. When converting an external table to managed, Databricks copies the data and transaction log into the managed storage location you have set. This approach enables a single source of truth across analytics and AI workloads while satisfying compliance, cost allocation, and data residency requirements."
---

# Your data, your storage, your rules: a 2026 guide to storing Unity Catalog managed tables

[Databricks](https://yomu.fyi/company/databricks) · Elizabeth Bowman, Isabel Dong · Sep 29, 2026

**Type:** Explainer

## Summary

Unity Catalog managed tables let you control where your data physically resides while keeping it in cloud storage you own, such as S3, ADLS, or GCS, unlike platforms that store tables in provider-controlled storage. You set managed storage locations at the metastore, catalog, or schema level, with the most specific level winning, and can change where new tables land using ALTER CATALOG or ALTER SCHEMA commands. Managed tables use open formats including Iceberg and Delta, and external engines such as Apache Spark, Flink, and Trino can read and write through Iceberg REST Catalog and Unity Catalog open APIs. When converting an external table to managed, Databricks copies the data and transaction log into the managed storage location you have set. This approach enables a single source of truth across analytics and AI workloads while satisfying compliance, cost allocation, and data residency requirements.

## Context

The post addresses organizations that need to control the physical location of their Databricks table data for compliance, cost allocation, or administration, and explains how Unity Catalog’s managed tables provide that control while keeping data in open formats and customer-owned storage.

## Approach / What changed

Set managed storage locations at the metastore, catalog, or schema level using SET MANAGED LOCATION. To change where new tables land, use ALTER CATALOG … SET MANAGED LOCATION or ALTER SCHEMA … SET MANAGED LOCATION. Converting an external table to managed copies data into the current managed storage location.

## Takeaways

- Managed table data resides in cloud storage you own (S3, ADLS, GCS), not in Databricks-controlled storage.
- Storage location can be set at metastore, catalog, or schema level, with the most specific level taking precedence, and can be changed after setup using ALTER CATALOG or ALTER SCHEMA commands.
- External engines can read and write managed tables through open APIs (Iceberg REST Catalog, Unity Catalog Open APIs) without duplicating data.

## FAQ

### Where does Unity Catalog store managed table data, in Databricks-owned storage or my own cloud account?

In your own account. Managed table data is written to cloud storage in your own account, whether S3, ADLS, or GCS, at a managed storage location you set on your metastore, catalog, or schema. Databricks manages the table's layout and lifecycle, but the underlying files live in a bucket or container you own and register with Unity Catalog, not in a Databricks-controlled account.

### Do Unity Catalog managed tables lock me into Databricks?

No. Managed tables use open table formats including Iceberg and Delta that stay in cloud storage you own. External engines can write to and read from them through the Iceberg REST Catalog and Unity Catalog's open APIs, so your data isn't trapped behind a proprietary interface. You keep ownership of the storage, the data stays in open formats, and access happens over open standards.

### Can I keep certain data in separate storage for compliance or data residency?

Yes. You can give a specific catalog or schema its own managed storage location, separate from everything else if need be, to keep data for different countries or regulatory regimes in distinct storage, or to attribute storage costs to a particular team or business unit.

**Tags:** [Databricks](https://yomu.fyi/topic/databricks), [Data Governance](https://yomu.fyi/topic/data-governance), [Delta Lake](https://yomu.fyi/topic/delta-lake), [Iceberg](https://yomu.fyi/topic/iceberg), [Unity Catalog](https://yomu.fyi/topic/unity-catalog)

- Source: [Databricks](https://www.databricks.com/blog/your-data-your-storage-your-rules-2026-guide-storing-unity-catalog-managed-tables)
- Source URL: https://www.databricks.com/blog/your-data-your-storage-your-rules-2026-guide-storing-unity-catalog-managed-tables
- Ingested by Yomu: 2026-09-29T21:00:07.544Z

[Read original post](https://www.databricks.com/blog/your-data-your-storage-your-rules-2026-guide-storing-unity-catalog-managed-tables)