Refactor a Monster Model Into Layered dbt Steps
Refactor one oversized dbt model into staging, intermediate, and mart responsibilities.
The team fears touching fct_revenue_all_in_one because it carries too many business and source responsibilities at once. Refactor by decision boundary: isolate reusable concepts, validate them independently, and keep the final mart thin. The trap is splitting a large file mechanically without changing the underlying coupling. Step 1 · Inventory the hidden decisions Mark which parts of the SQL are raw cleanup, reusable business concepts, and published reporting shape. This reveals where the real split boundaries are. You are looking for reasons for change, not equal-sized files. Step 2 · Extract one reusable concept Move refund normalization and FX conversion into…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in