OFICIAL Databricks Newsroom

Modernizing SQL ETL in Lakehouse with Declarative Patterns

What happened
Based on Databricks Newsroom · Aug 25, 2026

Databricks is introducing declarative SQL ETL patterns in Lakehouse, enabling SQL analysts to define append, CDC, and batch overwrite operations directly in their queries without dedicated pipeline tools.

Modernizing SQL ETL in Lakehouse with Declarative Patterns
Databricks Newsroom — Databricks
Key points
·
How SQL analysts and analytics engineers can now leverage declarative flows for append, CDC, and batch ETL directly in their queries.
·
Databricks is bringing declarative ETL to data warehousing workflows in Lakehouse, making it easier for SQL practitioners to simplify complex transformation logic in familiar places they already work.
·
This is part of a broader strategy to bring the declarative execution model behind Apache Spark™ Declarative Pipelines into more authoring experiences across Databricks.
·
Instead of needing to work in a dedicated pipelines-oriented environment, SQL users can now define common ETL patterns directly within their SQL queries in Databricks Lakehouse.

Databricks is expanding declarative ETL capabilities within Lakehouse, allowing SQL practitioners to define common transformation patterns such as append operations, change data capture (CDC), and batch overwrites directly in their SQL queries. This initiative aligns with the company’s broader effort to integrate the declarative execution model of Apache Spark™ Declarative Pipelines into more authoring environments. Previously, such patterns required manual scheduling, custom SQL logic, or separate pipeline tools, but now users can describe the desired outcome in SQL while Databricks manages scheduling, refresh, and incremental processing automatically.

The new declarative operations include append-only updates for incrementally adding new records, AUTO CDC for handling inserts, updates, and deletes with minimal code, and REPLACE WHERE for targeted batch recomputation. Append flows track new versus processed data automatically, while AUTO CDC simplifies complex MERGE INTO logic by specifying keys, sequencing, and delete handling. REPLACE WHERE enables selective reprocessing of subsets of data, such as date ranges or partitions, with Databricks’ Enzyme engine optimizing performance by processing only changed data, reducing runtime and costs.

These declarative patterns are accessible directly in the Lakehouse SQL Editor, where users can define flows that refresh on a schedule, trigger from upstream updates, or run on demand. The approach supports incremental state management, dependency handling, and schema evolution without requiring a full rewrite of existing SQL workflows. Teams can continue using fine-tuned procedural SQL for custom tasks while leveraging declarative operations for recurring, maintenance-heavy patterns, offering a practical path to modernization.

For larger or more complex projects, Databricks continues to recommend the Lakeflow Pipelines Editor, which provides a project-oriented environment with multi-file development, dependency management, pipeline visualization, and integrated validation. This dual approach allows SQL teams to start small with declarative primitives in their existing workflows and scale up as needed, blending traditional SQL control with automated, low-friction ETL management.

Original source → Deals on Clipraptor.com →