Menu

Data modeling course · Lesson 1 of 11

Data Warehousing for Data Engineers

A complete introduction to data warehousing: dimensional modelling, grain, facts and dimensions, slowly changing dimensions, data layout, ELT and serving trustworthy reports.

  • Beginner
  • Pillar guide
  • 2 min read
  • Updated Oct 2026
On this page
  1. 1. Dimensional modelling
  2. 2. Grain first
  3. 3. History: slowly changing dimensions
  4. 4. Loading: ELT and idempotency
  5. 5. Physical layout
  6. 6. Platforms
  7. 7. Trust
  8. Checkpoints

A data warehouse organises data for answering questions, not for running transactions. Its value comes from good modelling, reliable loading and trustworthy definitions more than from any particular product.

1. Dimensional modelling

Separate facts (measurements of events, at a stated grain) from dimensions (the descriptive context you filter and group by). Arranged as a star schema, every query follows the same simple pattern: join the fact to a few dimensions, group and aggregate.

Read: Facts, dimensions and the star schema

2. Grain first

The grain is what one fact row means: one order line, one account per day. Decide it before designing columns. Mixed grains cause double counting.

3. History: slowly changing dimensions

When attributes change, overwrite (Type 1) or version (Type 2) them. Type 2 needs surrogate keys, validity ranges and a rerunnable load.

Read: Slowly changing dimensions

4. Loading: ELT and idempotency

Most modern warehouses load raw data first and transform with SQL in layers (raw, staging, marts). Every load must be safe to rerun.

Read: ETL vs ELT · Idempotency in pipelines

5. Physical layout

Partition large tables by their main filter (usually date), cluster by the next most common filters, and keep files large.

Read: Partitioning, clustering and data layout

6. Platforms

Cloud warehouses separate storage from compute; lakehouses add warehouse guarantees to lake storage. Learn one platform well.

Read: Lake vs warehouse vs lakehouse · Snowflake architecture

7. Trust

Tests on keys and relationships, reconciliation with sources, certified metric definitions and visible freshness are what make people believe the numbers.

Read: Data quality checks and contracts · Case study: Reporting and analytics platform

Checkpoints

Skill Checkpoint
Modelling Design a star schema for a business process and state its grain
History Write a Type 2 load that is safe to rerun
Loading Explain your layers and how each is tested
Layout Choose partition and clustering keys from query patterns

Practise with the e-commerce analytics platform project.

By Data Career Hub Editorial · Last reviewed Oct 2026 · Concepts are platform-neutral; examples in the linked guides were verified on SQLite 3.45

Progress is saved in this browser only. No account needed.

Search
Filter by type