Post

Friends don't let friends re-run unchanged SQL. It’s Day 2 of launch week and today we're launching the Prefect dbt Orchestrator. Every model, seed, test, and snapshot runs as a Prefect task. Caching, per-node retries, and the same alerting your other Prefect work uses.

Day two of three. See the full launch week: prefect.io/launch

1. Stop running the same SQL twice Each node’s SQL, config, macros, and upstream dependencies are hashed. If nothing changed, Prefect skips the node.

2. The DAG keeps moving when a model fails A staging model fails. Prefect retries that node without restarting the entire build. Other branches keep running.

3. Parallel execution without the overhead Prefect executes independent nodes concurrently instead of treating dbt build as one giant batch job.

4. dbt inherits Prefect’s orchestration primitives The same caching, retries, alerting, and visibility you use for Prefect flows now apply to dbt workloads.