What is a star schema in Power BI?

The data model design Microsoft recommends for Power BI, explained in plain English.

By Ihor Havrysh · Last reviewed May 2026

Eaglepedia mascot

A star schema is a way of arranging a Power BI data model into two kinds of table: fact tables, which hold the events being measured, and dimension tables, which hold the descriptive attributes used to filter and group those events. It is the model design Microsoft recommends for Power BI.

What a star schema is

A star schema is a pattern for organising the tables behind a report. Rather than one giant table, the data is split into a central table of events and a ring of smaller tables that describe those events. Microsoft's star schema guidance for Power BI calls it "the recommended modeling approach".

The name comes from the shape. Draw the central table in the middle and the descriptive tables around it, joined by lines, and the diagram looks like a star. Those two table types have proper names: fact tables in the centre and dimension tables around the outside.

A star schema is not a Power BI feature you switch on. It's a design choice you make when you build the semantic model, the Power BI data model, deciding which tables hold what. Get that shape right and the rest of Power BI works with you rather than against you.

Fact tables: the events you measure

A fact table holds the things that happened: the events or observations you want to analyse. In a sales report, each row of the fact table is one transaction, with figures such as quantity sold and revenue alongside it.

Fact tables are usually the largest tables in the model, because a busy business generates a lot of events. They are mostly numbers: the measurable values you'll add up, plus a few key columns that link each row to the descriptive tables. There's little descriptive text in a fact table itself.

Dimension tables: the detail you slice by

A dimension table holds the descriptive detail: the "by what" you want to break the numbers down by. Common dimensions are Date, Product, Customer and Region. Each answers a question such as "sales by month" or "sales by product category".

Dimension tables are usually smaller than the fact table and full of descriptive columns: a Product table carries the product name, its category, its colour and so on. When you filter a report or drop a field onto a chart axis, you're nearly always using a dimension. The fact table supplies the numbers; the dimension tables give you the labels and the filters.

Why Power BI is built for the star schema

Power BI doesn't just tolerate the star schema; it's tuned for it. Three things all perform best when the model is shaped this way: the storage engine that compresses and holds the data, the relationships that carry a filter from one table to another and the way calculations are worked out.

Calculations are a clear example. Microsoft's DAX overview describes DAX, the formula language Power BI uses, and DAX measures evaluate fastest and most predictably over a clean star schema. When a filter on a dimension flows cleanly to the fact table, a measure has a simple, fast path to follow.

The practical payoff is reports that stay quick, files that stay small and measures that behave the way you expect. A model that fights the star schema tends to be slow and unpredictable instead.

The star schema versus the alternatives

The most common alternative is a single flat table: every column in one wide sheet, much like a large Excel export. For a tiny dataset that's fine. At any real scale it slows down, repeats the same descriptive text on thousands of rows and makes calculations harder to write and filtering harder to predict.

A snowflake schema is the other contrast. It still has fact and dimension tables, but the dimensions are normalised further into linked sub-tables, so there are more relationships to hop through. In Power BI a star schema is generally preferred: it's simpler to build and to reason about while giving the same answers. Shaping the star is a loading job. The Power Query step is where tables are split and joined into the star shape before they reach the model.

A good model is where good Power BI begins Reading about the star schema is a useful start; designing one from your own messy data is a skill worth building properly. Our two-day, hands-on Power BI Masterclass teaches data modelling the practical way, shaping real tables into a star schema rather than learning the theory in the abstract. If you are weighing up where to learn, our Power BI training buyer's guide compares the UK options.

Frequently asked questions

Both organise data into fact and dimension tables. In a star schema each dimension is a single table. In a snowflake schema a dimension is split further into linked sub-tables, which adds more relationships. A star schema is flatter and simpler; a snowflake schema is more normalised. In Power BI a star schema is usually preferred.

The star schema. Microsoft recommends it as the optimal model design for Power BI, because the storage engine, the relationships between tables and DAX calculations all perform best with that shape. A snowflake schema works, but the extra tables add complexity for little gain in most reports.

Yes. The star schema is a decades-old idea, but it remains Microsoft's current recommended approach for Power BI and Fabric semantic models. It has not been replaced by anything newer; modern tools are still built around it, so it is as relevant today as ever.

For a tiny dataset, a single flat table can be fine. The benefits of a star schema grow with the data: faster reports, smaller files, simpler DAX and clearer filtering. Building to a star schema from the start is a good habit, because a report that starts small often grows.
Ihor Havrysh - Software Engineer at Red Eagle Tech

About the author

Ihor Havrysh

Software Engineer

Software Engineer at Red Eagle Tech with expertise in cybersecurity, Power BI, and modern software architecture. I specialise in building secure, scalable solutions and helping businesses navigate complex technical challenges with practical, actionable insights.

Read more about Ihor

Discovery call

A friendly 15-minute video call with Kat to understand your needs. No preparation needed.

  • Discuss your project
  • Get honest advice
  • No obligation
Kat Korson, Founder of Red Eagle Tech

Kat Korson

Founder & Technical Director

Our team has 10+ years delivering software solutions for growing businesses across the UK.

Send us a message

Your information is secure. See our privacy policy.

Find us