DatabricksBenjamin Mathew, Prakhar Jain, Sumeet VarmaAnnouncement
Transactions are Generally Available, advancing warehousing on the Lakehouse
Summary
Databricks made multi-statement transactions generally available on Delta Lake and Apache Iceberg tables, providing atomic guarantees for complex, multi-step workflows directly on the lakehouse. Previously, organizations had to rely on separate warehouse systems for these transactional guarantees, adding expensive data movement, duplicate copies, fragmented governance, and custom consistency workarounds. Row-level concurrency enables concurrent transactions to write to the same table as long as they do not update the same row, delivering significantly stronger performance than traditional cloud and legacy warehouses. The transactions are composable with stored procedures, temporary tables, and streaming tables, and they respect Unity Catalog attribute-based access controls including row-level security and column masking on both reads and writes. Fivetran used transactions to remove consistency-repair code for its slowly changing dimension updates using SCD Type 2, and Accolade processes roughly 1,700 transactions daily for claims and liabilities on the governed lakehouse.
Context
Organizations historically relied on separate warehouse systems for multi-table transactional guarantees, incurring data duplication, fragmented governance, and custom consistency workarounds.
Approach / What changed
Databricks introduced native multi-statement transactions on Delta Lake and Apache Iceberg tables, supporting row-level concurrency, Unity Catalog integration, stored procedures, temporary tables, and SQL scripting, enabling warehouse workloads on the lakehouse.
Takeaways
Multi-statement transactions are natively supported on both Delta Lake and Apache Iceberg tables, allowing atomic guarantees across tables without moving data to a proprietary format.
Row-level concurrency enables multiple transactions to write to the same table simultaneously as long as they target different rows, outperforming lock-based serialization in high-throughput scenarios.
Transactions integrate with Unity Catalog for attribute-based access control (row-level security and column masking) on both reads and writes, and provide observability via DESCRIBE TABLE, SHOW COLUMNS, and GET DIAGNOSTICS.
FAQ
How do multi-statement transactions handle concurrent writes?
They use row-level concurrency, allowing multiple transactions to write to the same table concurrently as long as they do not update the same row, avoiding lock-based serialization and enabling higher throughput.
What table formats are supported?
Both Delta Lake and Apache Iceberg tables are supported, preserving open table formats without requiring data movement into a proprietary format.
How do transactions interact with Unity Catalog?
Transactions respect Unity Catalog attribute-based access controls, including row-level security and column masking, on both reads and writes, ensuring governed access even during complex workflows.
Source and freshness
- Source
- databricks.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.