CSE Roadmap

Specialist tier · about 3 hours · 5 parts

Part 1 of 5 · 1 min read

Why this page comes first

In this module you will

  • Distinguish valid time from transaction time with a concrete example.
  • Design a table that keeps a full history of a changing value, instead of overwriting it.
  • Explain what a slowly changing dimension is, and why the name comes from data warehousing.
  • Close out Level 3 able to decide when a plain, non-temporal table is simply not enough.

This is the last module of Level 3. Every earlier module modeled the current state of things. Some real questions, like "what was this customer's address when they placed this specific order," need the past preserved too, not just overwritten.