Register Lakebase in Unity Catalog

Register Lakebase in Unity Catalog is a Databricks data governance capability, introduced June 2025.

Registers a Lakebase Postgres database as a read-only Unity Catalog catalog, so analytical access to its schemas, tables, and views is governed by Unity Catalog grants and can be joined with lakehouse data in cross-source queries.

• It puts your Postgres database in Unity Catalog as a catalog you can look at but not touch; every write still has to go through Lakebase itself. 🔗
• Only serverless compute is invited; point a Pro or classic SQL warehouse at the catalog and it is turned away. 🔗
• Branch a registered database and the branch inherits its parent's registration metadata, which is exactly why registering that branch as its own catalog then fails. 🔗

⚠ Limitations: Registered catalogs are read-only, can be queried only from a serverless SQL warehouse or serverless notebook and job compute (not Pro or classic warehouses or classic compute), map one catalog to one Lakebase database, serve cached metadata that may need a manual refresh, and a branched database cannot be registered as a separate catalog. 🔗

Category

Data governance

Introduced

June 2025🔗

Also known as

Lakebase catalog, Database catalog

Verified

2026-10-14