Recommended Free Tools
No: dbt has not stopped running transformations in cloud data warehouses. dbt Labs describes dbt v2 as a single Rust-based engine, but its documented engine still connects to remote data platforms through adapters and executes model workflows there. The important change is the engine and the way teams develop and orchestrate projects—not the disappearance of warehouse execution.
For teams assessing readiness, the practical questions are whether their adapter is mature enough, whether their project behaves as expected on the new engine, and whether their workflows, licensing needs, and warehouse-cost assumptions still fit.
As an Amazon Associate I earn from qualifying purchases.
What does “leaving the warehouse” actually mean?
The phrase can suggest that dbt is moving transformations out of the warehouse. That is not what dbt Labs’ documented architecture describes. The engine validates project code, builds a directed acyclic graph (DAG) of dependencies, connects to remote data warehouses through adapters, executes the DAG, and produces logs and metadata. Warehouse execution remains part of that design.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesWhat is changing is the engine underneath the dbt experience. In its September 16, 2026 announcement, dbt Labs said dbt v2 was generally available as one modern Rust-based engine, informed by the Fusion work. The company said the new engine replaces the friction of maintaining two engines; that statement is about engine consolidation, not a move away from warehouse-based transformations.
#1 Best Overall
What is the status of dbt v2 and its adapters?
As of dbt Labs’ September 16, 2026 announcement, the company described dbt v2 as generally available. The announcement listed adapter maturity separately, so v2 availability should not be read as a guarantee that every platform adapter is equally ready.
| Adapter or platform | Status in dbt Labs’ September 16, 2026 announcement |
|---|---|
| BigQuery | Generally available |
| Databricks | Generally available |
| DuckDB | Generally available |
| Redshift | Generally available |
| Snowflake | Generally available |
| ClickHouse | Beta; available for local installation and testing |
| Spark | Beta; available for local installation and testing |
| Athena | Described as coming soon |
| Fabric | Described as coming soon |
| Postgres | Described as coming soon |
This is a dated vendor snapshot, not a lasting compatibility guarantee. Before planning a rollout, check dbt’s current adapter and upgrade documentation for your platform and authentication method.
Do you need to migrate from dbt Core?
Not solely because dbt v2 is available. In the September 2026 announcement, dbt Labs referred to dbt Core as the previous version, dbt v1, and said Core remains Apache 2.0. That announcement does not establish that every Core project must migrate immediately or that every project will work identically after a move. A decision should depend on your adapter, project features, operational requirements, and distribution or licensing needs.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchRank #2
Check these six areas before changing production pipelines
1. Map every project to its adapter and authentication method
List each production project, its warehouse, adapter, authentication method, and deployment environment. Compare every adapter with its current status rather than treating the engine’s general availability as proof that your specific connection path is ready. If an adapter is in beta or not yet generally available, test it in a non-production environment before making it part of a production plan.
2. Test the features your project actually uses
Inventory macros, project configuration, tests, materializations, packages, and less-common behaviors. Earlier dbt Labs material about the Fusion engine said it aimed to support most Core functionality, but did not promise identical behavior for logs, metadata, or every runtime detail. That is useful context, not a complete compatibility matrix for current v2. Use current upgrade guidance and run a representative copy of your project to verify the features that matter to you.
3. Validate operational contracts, not just successful model builds
A pipeline can build models and still break something downstream if its surrounding workflow changes. Exercise the command-line workflows, selectors, CI checks, schedules, logs, metadata outputs, and observability integrations your team depends on. Confirm that downstream consumers still receive the signals and artifacts they expect, and that the order of execution respects the project’s dependencies.
4. Confirm where queries run and what they consume
Check which warehouse executes each query, which permissions it uses, what compute it consumes, and what events trigger a build or rebuild. dbt Labs describes dbt models as warehouse transformations and says state-aware orchestration can avoid some unnecessary work. Measure the effect against your own workload, including any changes to run frequency, warehouse sizing, freshness targets, or rebuild behavior.
5. Review freshness and reuse rules
dbt Labs says dbt State checks warehouse metadata and model SQL to determine whether a run should build, skip, clone, or defer work. Work out whether those reuse choices satisfy each model’s freshness expectations and data-product service-level agreements. A model that can be reused technically may still need rebuilding sooner to meet a downstream consumer’s requirements.
6. Choose the distribution that fits your licensing needs
The September 2026 announcement distinguished two distributions: dbt, described as a superset with SQL comprehension and optional paid features such as dbt State, and dbt-oss, which includes Apache-licensed components. dbt Labs said dbt Core remains Apache 2.0. Review the current distribution documentation and licensing terms for the exact components and use case you plan to run; do not assume one distribution’s licensing description applies to every component in the other.
Rank #4
Could dbt v2 lower warehouse costs?
Potentially, but the figures dbt Labs has published describe different reported results and should not be combined into a promised saving for a typical user.
- In its September 16, 2026 announcement, dbt Labs reported an average 15–30%+ reduction in warehouse compute for dbt State. This is a vendor-reported claim, not an independent benchmark.
- The same announcement quoted RxBenefits as reporting a 59% reduction in scheduled-job warehouse costs and reuse of more than 700,000 models on a Snowflake adaptive warehouse. The result was attributed to Chris Shepherd, Principal Data Engineer at RxBenefits, and is a customer-reported outcome.
- In a January 2026 cost-efficiency article, dbt Labs reported 895,000 scheduled jobs per day and observed 30% of models reused under state-aware orchestration. These are company-reported workload and reuse figures, not an estimate of the saving a particular team will achieve.
The results concern different populations, workloads, and measures. For your own estimate, compare warehouse usage and costs before and after a controlled rollout, while keeping workload volume, scheduling, and freshness requirements in view.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →A practical rollout sequence
- Check the current upgrade guidance. Confirm current availability and requirements for your adapter, distribution, authentication method, and target environment.
- Select a representative project. Include the macros, materializations, packages, tests, and less-common behaviors that production teams rely on.
- Run compatibility checks outside production. Compare model results and exercise CI, selectors, schedules, logs, metadata, and observability integrations.
- Verify execution and reuse. Confirm which warehouse queries run against, what triggers rebuilds, and whether freshness and state-based reuse behavior meet downstream expectations.
- Compare measured outcomes. Record relevant runtime, warehouse usage, and operational behavior under comparable workloads before expanding the rollout.
dbt Labs also quoted RMIT University delivery lead Vishesh Jain describing improvements in the development experience with the v2 engine. That customer testimonial is useful context, but it does not establish how a particular project or warehouse workload will perform.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
