Bridge keys and fact grain: when to split facts instead of flattening dimensions
The article argues that many-to-many relationships between dimensions should be modeled explicitly, using a bridge table or a clearly defined fact grain rather than convenience views that hide the grain. It notes that flattened gold-layer views cause dashboards to double count, fail to reconcile across pages, and break for role-playing dimensions. The author recommends promoting bridge keys to first-class, validated columns, sharing matching logic across fact tables, and aligning foreign key types. Remodeling the fact table is presented as the priority before refining report visuals. The piece also advises documenting each row's grain and splitting tables when they contain two distinct business truths.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in