Data Warehousing Concepts
Learn how data warehouses differ from lakes and marts, compare Inmon and Kimball architectures, and model star and snowflake schemas.
A data warehouse supports analysis across an organization, and setting one up involves a series of design decisions. The lessons work through those decisions: how a warehouse differs from a data lake or a data mart, how the top-down approach of Bill Inmon and the bottom-up approach of Ralph Kimball shape its architecture, how fact and dimension tables form star and snowflake schemas, and when ETL or ELT and cloud or on-premise setups make sense.
What You Will Achieve
- Decide whether a data warehouse, data lake, or data mart suits a given analysis need
- Compare top-down and bottom-up warehouse designs and choose one for a project
- Build a star or snowflake schema and handle slowly changing dimensions in it
- Match ETL or ELT, OLAP or OLTP, and cloud or on-premise options to a scenario’s requirements
Program Overview
Data Warehouse Basics and Architectures
Defines a data warehouse against similar technologies, then turns to its layers, the architectural approaches behind it, and the system types it works alongside.
- Data warehouses compared with data lakes and data marts
- Life cycle stages and the roles that support them
- Warehouse layers, ETL, and the presentation layer
- Inmon and Kimball approaches, OLAP and OLTP systems
Data Modeling for the Warehouse
Shows how to organize warehouse data with a dimensional model and how the storage format affects which queries run faster.
- Fact and dimension tables in star and snowflake schemas
- Kimball’s four-step process and deciding on the grain
- Slowly changing dimension types I, II, and III
- Row versus column data stores
ETL, ELT, and Implementation Choices
Weighs options for loading and hosting warehouse data, then closes with a worked design example that connects the earlier decisions.
- ETL compared with ELT
- Data cleaning and data governance
- On-premise and cloud data warehouses
- A data warehouse design example
Certificate Awarded (Paid)
Job Outlook
These concepts apply wherever teams plan, build, or query a data warehouse, including data engineering work and the analyst and data scientist roles that rely on the warehouse’s presentation layer.
Good for: Analysts, data scientists, and aspiring data engineers who want the vocabulary and design trade-offs of data warehousing before they join a warehouse project.
Keep in mind: Despite the intermediate label, it is an introductory and conceptual course, and the closing design example is worked through as a series of decisions rather than a build.
Bottom line: A compact grounding in warehouse design that ties Inmon, Kimball, schemas, and loading choices to short scenario exercises.
Frequently Asked Questions
How does the course contrast Inmon and Kimball?
It sets Bill Inmon's top-down approach against Ralph Kimball's bottom-up approach and covers the characteristics of each. Exercises ask you to choose the approach that fits a scenario, and the closing design example takes the bottom-up route.
Which slowly changing dimension types are covered?
The data modeling chapter covers types I, II, and III, with a pop quiz and an exercise on how they differ. It sits alongside Kimball's four-step process for building a dimensional model and choosing its grain.
What examples do the exercises use?
An early exercise looks at possible use cases of a data warehouse for Zynga. Later ones put you in a consultant's shoes and ask you to sort scenarios, such as row versus column store cases and OLAP versus OLTP situations.
Do the videos have transcripts?
Yes. Each video has a live transcript you can reveal with the Show transcript control in the player, and a course glossary is available in the resources section beside the lessons.


There are no reviews yet.