We built dbt State to stop rebuilding what hadn't changed
Summary
dbt State is now generally available across every environment where you run dbt, letting teams skip rebuilding models that haven't changed since the last run. The result is lower compute spend and faster iteration cycles during development.
Summary generated by brickster.ai. For the full article, follow the source link above.
More from dbt Labs Blog
Fivetran + dbt Labs Announces New Capabilities to Make Enterprise Data Agent-Ready at dbt Summit 2026
Fivetran and dbt Labs used dbt Summit 2026 to announce GA for dbt v2 and dbt State, alongside new capabilities including the Fivetran Context Layer, dbt Charts, and a broader open lakehouse vision. Together the releases push toward making enterprise data agent-ready, giving Databricks practitioners new tooling for orchestration, state management, and visualization within the lakehouse.
Everything we announced at dbt Summit and why it matters
Databricks unveiled its full dbt Summit lineup, including dbt v2, dbt State, dbt Wizard, and dbt Charts. This roundup breaks down what each product does and the specific problem it solves for teams building on dbt.
Celebrating the 2026 dbt partner of the year winners
dbt Labs named its 2026 Partner of the Year winners: phData, Snowflake, Cívica, Datum Studio, and 66degrees. For Databricks practitioners tracking the broader analytics-engineering ecosystem, it's a signal of which implementation and platform partners dbt Labs sees as driving the most impact this year.
Why your AI pilot stalled at the context gap
Most AI pilots don't stall because of weak models — they stall because the system lacks trusted context, and this post lays out how to close that gap. It reframes context as the foundation Databricks teams need to build before scaling AI initiatives past the pilot stage.
Scaling AI is easy. Trusting it is hard.
As AI initiatives scale, weak data trust and governance are often the first things to crack, exposing gaps that undermine reliability before models even get the blame. This post examines where those failures typically originate and what it takes to shore up governance so scaling doesn't outpace trust.
Databricks processes your data. dbt defines what it means
Databricks handles compute while dbt governs the transformation logic that defines what the data actually means — yet organizations routinely bundle these as a single approval decision. The post argues executives should treat the platform choice and the transformation-logic choice as separate decisions, not one.