Module 12: MetricFlow and the dbt Semantic Layer
See how dbt semantic models produce governed SQL at query time.
115 minutes. 1 inline exercise. Free course module.
Learning Objectives
- Understand semantic model YAML at a high level
- Know what MetricFlow does
- Explain how governed metrics can serve BI, apps, and AI
Why This Matters
MetricFlow powers the dbt Semantic Layer by using semantic model and metric definitions to generate SQL dynamically for requested metrics and dimensions.
Lesson Content
The Mental Model
MetricFlow powers the dbt Semantic Layer by using semantic model and metric definitions to generate SQL dynamically for requested metrics and dimensions.
You define the rules once. MetricFlow acts like a careful translator that writes the SQL for each question using those rules.
Tiny Example
We will use a small ecommerce dataset throughout the course. Think of these as the only tables in your first warehouse:
| Table | Grain | Example columns |
|---|---|---|
raw_orders | one row per order event | order_id, customer_id, amount, status, created_at |
raw_order_items | one row per item inside an order | order_id, product_id, quantity, item_price |
raw_customers | one row per customer | customer_id, email, country, created_at |
Interactive Check
Question: Why is generated SQL safer than each dashboard author writing their own revenue SQL?
Reveal the answer
The generated SQL comes from one governed metric definition, so all tools use the same calculation, joins, and time rules.
Inline Practice Lab
This lab is intentionally small. You can solve it by reading the table, writing the SQL/YAML mentally, or pasting the snippet into any SQL scratchpad later.
-- Example starter table
select
order_id,
customer_id,
amount,
status,
created_at
from raw_orders;The goal is not tooling setup. The goal is learning the production habit: state the grain, clean one thing, test one assumption, and explain the downstream impact.
Self-Check Quiz
- What is the grain of the table you are building?
- Which downstream metric or dashboard would be wrong if this model broke?
- What test would catch the most likely beginner mistake here?
Real-World Use Cases
- Reliable executive dashboards that do not disagree across teams
- AI analytics agents that query governed metrics instead of guessing SQL
- Auditable metric changes where owners can see downstream impact before merge
Production Notes
- Keep semantic definitions close to the dbt models they describe. Distance creates drift.
Common Mistakes
- Confusing measures and metrics
- Creating semantic definitions on untested models
- Exposing dimensions that create unsafe joins
Think Like an Engineer
- Can you explain the grain of this model in one sentence?
- What breaks downstream if this field becomes null tomorrow?
- Where should this logic live so it is reused instead of copied?
Career Relevance
Analytics engineering is the bridge between SQL skill and production data ownership. Freshers who learn tests, lineage, metrics, and semantic modeling early stand out because they can reason about trust, not just queries.
Key Terms
- MetricFlow
- The query engine used by the dbt Semantic Layer to generate metric SQL.
- Semantic model
- A definition that describes entities, measures, and dimensions for a dbt model.
Inline Exercises
-
Read a Semantic Model YAML
Identify entities, measures, dimensions, and metrics in a simplified YAML snippet.
30-45 minutes - Beginner to Intermediate
- Circle the primary entity
- Find the revenue measure
- Find the order date time dimension
- Find the revenue metric
- Explain how a query could ask for revenue by month
Inline lab: complete the exercise directly in the course page.
Key Takeaways
- MetricFlow generates SQL from semantic definitions
- The dbt Semantic Layer connects governed metrics to many consumers
- Semantic YAML should be reviewed like production code