With dbt State, stop rebuilding what didn't change

dbt State, now generally available, reduces data warehouse compute costs and runtimes by evaluating each dbt model’s compiled logic and upstream data freshness, then reusing an existing result, cloning a valid result from another schema, or rebuilding only when necessary. It applies this “cheapest valid action” approach at the model level across development, CI, and production environments, allowing multiple jobs to benefit from previously validated builds. Teams can customize behavior through settings such as lag tolerance, source freshness requirements, and code comparison options, while dbt state explain clarifies why individual nodes were reused, cloned, skipped, or built. The feature is less effective for views using select *, nondeterministic Jinja code, and certain BigQuery external sources without freshness metadata. Customer examples cited in the post report reduced model builds, lower warehouse costs, faster iterations, and more frequent pipeline updates, while dbt Cost Insights provides estimates of State-related spending and savings across supported warehouses.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.