Convert a legacy SQL script or view into a dbt model and prove parity
When a scheduled SQL script is the real production logic and nobody can prove a rebuild would match it.
- Transformation
Larger outcome
9 RecipesEverything you own that still works and nobody wants to touch: stored procedures, views, notebooks, scalar functions and managed connectors. Each one is rebuilt with parity proved rather than assumed.
When a scheduled SQL script is the real production logic and nobody can prove a rebuild would match it.
When the nightly load is a stored procedure nobody fully understands anymore.
When a materialized view refreshes on a schedule nobody wrote down and downstream reports assume that cadence.
When a transformation only exists as a notebook someone runs by hand before the numbers go out.
When a Spark notebook is the only thing that lands a source into bronze and nobody can run it unattended.
When a scalar SQL function is called from a dozen models and lives outside version control.
When the connector bill changed shape, or the connector has been broken with a pending fix for weeks.
When the warehouse is changing and the dbt project has to follow it.
When Fabric is the mandate and the estate is hundreds of packages nobody wants to open.