Star schema concept in Power BI - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a star schema in Business Intelligence?

A star schema is a simple database design that organizes data into one central fact table connected to multiple dimension tables, like points of a star.

beginner

What is the role of the fact table in a star schema?

The fact table stores measurable, numeric data like sales or quantities, and keys that link to dimension tables.

beginner

Name three common dimension tables in a star schema for sales data.

Common dimension tables include Date (time), Product, and Customer.

beginner

Why is the star schema easy to understand and use?

Because it has a clear, simple structure with one fact table in the center and related dimension tables around it, making queries straightforward.

intermediate

How does a star schema improve report performance in Power BI?

It reduces complex joins by having simple relationships, which helps Power BI process queries faster and makes reports more responsive.

In a star schema, what type of data is stored in the fact table?

A Only text data

B Numeric measures and keys

C Descriptions and categories

D Unrelated data

The fact table holds numeric measures like sales amounts and keys linking to dimension tables.

Which of these is NOT a typical dimension table in a star schema?

A Sales Amount

B Product

C Date

D Customer

Sales Amount is a measure stored in the fact table, not a dimension table.

What shape does the star schema resemble?

A Star

B Circle

C Triangle

D Square

The schema looks like a star with a central fact table and dimension tables around it.

Why do star schemas help improve query speed in Power BI?

A Because they store data in one big table

B Because they use many complex joins

C Because they have a simple, clear structure

D Because they avoid using keys

The simple structure reduces complex joins, making queries faster.

Which table in a star schema contains foreign keys to dimension tables?

A Reference table

B Dimension table

C Lookup table

D Fact table

The fact table contains foreign keys linking to each dimension table.

Explain the structure of a star schema and why it is useful in Power BI.

Think about how a star looks and how data is organized around a central point.

Describe the difference between fact tables and dimension tables in a star schema.

Consider what kind of data each table stores and their roles.

Practice

1. What is the main characteristic of a star schema in Power BI?

easy

A. A single table with all data combined

B. Multiple fact tables connected in a chain

C. One central fact table connected to multiple dimension tables

D. Only dimension tables without any fact table

Solution

1. Step 1: Understand star schema structure

   A star schema has one main fact table that stores measurable data.

2. Step 2: Identify dimension tables role

   Dimension tables provide descriptive attributes and connect to the fact table.

3. Final Answer:

   One central fact table connected to multiple dimension tables -> Option C

4. Quick Check:

   Star schema = One fact + many dimensions [OK]

Hint: Remember star schema looks like a star with one center [OK]

Common Mistakes:

• Thinking multiple fact tables form a star schema
• Confusing dimension tables as fact tables
• Assuming star schema has no fact table

2. Which of the following is the correct way to describe the relationship in a star schema?

easy

A. One-to-many from dimension tables to fact table

B. Many-to-many between fact and dimension tables

C. One-to-many from fact table to dimension tables

D. One-to-one between fact and dimension tables

Solution

1. Step 1: Identify relationship direction

   Dimension tables filter many rows in the fact table, so one dimension row relates to many fact rows.

2. Step 2: Confirm relationship type

   This means a one-to-many relationship from dimension to fact table.

3. Final Answer:

   One-to-many from dimension tables to fact table -> Option A

4. Quick Check:

   Dimension to fact = one-to-many [OK]

Hint: Dimension filters many facts, so one-to-many from dimension [OK]

Common Mistakes:

• Reversing the relationship direction
• Choosing many-to-many which is not typical in star schema
• Assuming one-to-one relationships

3. Given a star schema with a Sales fact table and a Product dimension table, what happens if you slice sales by product category?

medium

A. The report shows total sales without any filtering

B. Sales values are grouped by product category from the dimension table

C. Sales values are ignored because categories are not in the fact table

D. An error occurs because dimension tables cannot filter facts

Solution

1. Step 1: Understand slicing in star schema

   Slicing by product category uses the Product dimension to filter the Sales fact table.

2. Step 2: Effect on sales values

   Sales are grouped and summed by the selected product categories.

3. Final Answer:

   Sales values are grouped by product category from the dimension table -> Option B

4. Quick Check:

   Slicing by dimension groups facts [OK]

Hint: Dimensions slice facts to group data in reports [OK]

Common Mistakes:

• Thinking dimension filters do not affect fact data
• Assuming error occurs when slicing by dimension
• Believing sales values are ignored

4. You created a star schema but your report shows incorrect totals when filtering by a dimension. What is the most likely cause?

medium

A. The report uses a pie chart instead of a bar chart

B. The fact table has duplicate rows

C. The dimension table has too many columns

D. The relationship between fact and dimension tables is inactive or missing

Solution

1. Step 1: Check relationships in star schema

   Inactive or missing relationships prevent filtering from dimension to fact table.

2. Step 2: Impact on report totals

   Without active relationships, filters do not apply correctly, causing wrong totals.

3. Final Answer:

   The relationship between fact and dimension tables is inactive or missing -> Option D

4. Quick Check:

   Active relationships needed for correct filtering [OK]

Hint: Verify relationships are active to fix filtering issues [OK]

Common Mistakes:

• Blaming duplicate rows without checking relationships
• Thinking chart type affects data filtering
• Ignoring relationship status

5. You want to optimize a Power BI model with sales data. Which star schema design improves query speed and report clarity?

hard

A. One large fact table with keys to small, focused dimension tables

B. Multiple fact tables with duplicated dimension data inside each

C. One fact table with all dimension attributes merged inside it

D. Only dimension tables with no fact table

Solution

1. Step 1: Understand star schema optimization

   A large fact table with keys to small dimension tables reduces data duplication and improves performance.

2. Step 2: Avoid poor designs

   Duplicating dimension data or merging all attributes in fact table causes slow queries and confusion.

3. Final Answer:

   One large fact table with keys to small, focused dimension tables -> Option A

4. Quick Check:

   Star schema = big fact + small dimensions [OK]

Hint: Keep fact big and dimensions small for best speed [OK]

Common Mistakes:

• Duplicating dimension data in fact tables
• Merging all data into one table
• Removing the fact table entirely