openskills.info
Course Preview

Dimensional Modeling and Star Schema Design

Dimensional modeling organizes analytical data around measurable events and the business context used to explain them. A star schema places one fact table at the center and connects it to dimension tables for filtering, grouping, and summarizing results.

itData engineering and analytics

Don't Panic: Dimensional Modeling and Star Schema Design

A dimensional model is a way to arrange analytical data so that the questions people ask have somewhere sensible to land. At the center sits a fact table, holding events or measurements. Around it sit dimension tables, holding the dates, products, customers, stores, and other context that make those measurements less like a sack of numbers and more like an answer.

The important bit is grain, meaning exactly what one fact row represents. This is the quiet bouncer at the door. If one row is an order line, line quantity belongs there. An order total does not, unless somebody writes down how it is allocated. Otherwise a perfectly respectable sum counts the same shipping charge once per line, which is how a spreadsheet acquires confidence it has not earned.

Facts and dimensions are not a contest between numbers and labels. Facts describe what happened, how often, or how much. Dimensions make those facts filterable and groupable. A surrogate key identifies one warehouse version of a dimension row, while the natural key identifies the source business entity. That split matters when history arrives, which it will, usually wearing a badge that says urgent.

For changing attributes, Type 1 overwrites the current value. Type 2 creates a new version, so old facts keep their old context and new facts receive the new key. The surprise is that correct SQL is not the same as correct meaning. Two fact tables can join without errors and still multiply measurements. Compare processes through conformed dimensions after each fact is summarized at compatible grain.

Start with the Intro when the star shape, fact patterns, and history rules need the longer explanation. Use Slides for the design sequence at a glance. Keep the Cheatsheet open while deciding grain, aggregation, keys, and verification queries. The Practice tab turns the sequence into a repeatable design method, and the Exercise gives one order-line star a chance to reveal whether its totals can survive contact with arithmetic.

Tools can draw the schema, load the tables, and run the query. None can decide what one row means. That remains the small, unfashionable, extremely consequential sentence at the start.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

Sources