Lakebase Change Data Feed: Sync Lakebase to Unity Catalog (Autoscaling)
Replicate Lakebase Autoscaling Postgres tables into Unity Catalog as managed Delta tables using Lakebase Change Data Feed (CDF), with full SCD Type 2 history.
Build with AI
- Copy the prompt below
- Paste into Cursor, Claude Code, Codex, or any coding agent
- Your agent builds it — asking questions along the way so the result is exactly what you want
New to templates? Learn more here
When done, you will have:
- Delta history tables in Unity Catalog with full change tracking for every insert, update, and delete
- Continuous CDC replication from Lakebase Autoscaling Postgres to the lakehouse with no external compute
- Operational data queryable in Spark SQL, notebooks, BI tools, and downstream pipelines
Prerequisites
Verify these Databricks workspace features are enabled before starting. Lakebase Change Data Feed (CDF, formerly Lakehouse Sync) is in Public Preview and has stricter workspace requirements than most other templates.
- A workspace on AWS or Azure in a Lakebase Autoscaling region. Change Data Feed is available in Public Preview on both AWS (
*.cloud.databricks.com) and Azure (*.azuredatabricks.net). A workspace admin must first enable the Lakebase Change Data Feed preview from the workspace Previews page. - A Lakebase Autoscaling project with tables. Run
databricks postgres list-projects --profile <PROFILE>and confirm your Autoscaling project appears. Anot enablederror means Lakebase is unavailable to this identity. This template does not cover project creation — see Create a Lakebase Instance if you need one. - Unity Catalog access. Run
databricks catalogs list --profile <PROFILE>and confirm the destination catalog and schema you want to replicate into are present. You will select them when enabling Change Data Feed.
