New: Cookbooks and AI ExplanationsStep-by-Step recipes to solve problems connected to Roadmaps and Cheat Sheets. Need more details? Use AI buttons for structured and simple explanations with concrete examples throughout the whole platform.Take a look
A customer upgrades their plan and suddenly every past order looks like it always belonged to the new plan.
What you'll have at the end
A dimension table with effective dates and a current flag where every past version of a row stays queryable.
You need
A dimension table already modeled as a star schema, with a natural key such as customer_id and at least one attribute whose past value matters for a report, like a plan tier or a region.
Not covered
Choosing which SCD type an attribute needs in the first place, or migrating years of already-overwritten Type 1 history back into version rows.
Checked 25 Aug 2026
Part of the Kimball Data Modeling cookbook