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
I have a table full of columns and no idea what should be a fact and what should be a dimension.
What you'll have at the end
A star schema for one process: the grain written as one sentence, plus its fact and dimension tables
You need
One wide table, such as an export or a query result, holding every column for one business process with no split into descriptive attributes and measured numbers yet.
Not covered
Sorting several flag or status columns into one shared dimension, which needs its own procedure once a table has more than a couple of them.
Collapse scattered order flags into one junk dimension
Come back here once the wide table has several flag or status columns instead of one identifier and a handful of descriptive ones.
Preserve customer history with a Type 2 slowly changing dimension
Use this once a dimension attribute built here, like a customer's tier, actually changes over time and the old value needs keeping.
Checked 25 Aug 2026
Part of the Kimball Data Modeling cookbook