· intermediate
Data Warehousing
The database built for analytics rather than transactions. Why columnar engines separate storage from compute, how to model for questions you have not been asked yet, and what actually drives the bill.
Written in house, from the work rather than from a syllabus. Every example is one we would use ourselves, and every quiz question explains why its answer is right.
What you’ll learn
- Explain why an analytics engine is built differently from a transactional one
- Describe what separating storage from compute changes operationally
- Model facts and dimensions, and choose a grain deliberately
- Handle attributes that change over time without losing history
- Load incrementally without duplicating or dropping rows
- Identify what drives warehouse cost, and reduce it
Before you start
- · SQL Foundations and Database Design, or equivalent
- · Data Engineering Foundations