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 total that should match last week's report is running about double, and nobody knows why.
What you'll have at the end
A corrected fact table grain, with a query that proves the double count is gone
You need
A fact table already joined to a dimension that keeps a history of changes, and a total from that join that looks off against what you expected.
Not covered
Deciding whether a dimension should keep history at all, or a doubled total caused by joining two fact tables together instead of one fact table to one dimension.
Leans on
Untangle a many-to-many relationship with a bridge table
Go there instead when the extra rows trace back to a genuine many-to-many link between the order table and a dimension, rather than a change history like this one.
Fix a fan trap that is doubling a revenue total
Reach for this one instead when two order tables get joined through a shared dimension, not one order table to a duplicated dimension row.
Checked 25 Aug 2026
Part of the Data Warehousing cookbook