BEGINNER · 8 MODULES · 64 LESSONS

Data Modeling for Analytics

Turn a flat data model into a real analytics warehouse, with dimensions that keep their history and tables your BI team can query without mistakes.

For you if
You already have a facts-and-dimensions model and need to turn it into a warehouse for BI.
By the end
You'll know how to choose star, snowflake, or one big table, track history with SCDs, and join facts at the right time.
You need
Intermediate SQL, basic Python, and the data engineering foundations guide or equivalent. Everything runs locally.
  1. 01From Flat Tables To Dimensional Models8 LESSONS
    1. Module introduction: from flat tables to dimensional models
    2. What foundations left flat, and why
    3. Kimball's four-step process
    4. Step 1: selecting Kiosko's business process
    5. Step 2: declaring the grain of fact_orders
    6. Steps 3-4: facts vs dimensions, a precise definition
    7. What changes when the grain is explicit
    8. Mini-project: Kiosko's grain declaration
  2. 02The Star Schema And Conformed Dimensions8 LESSONS
    1. Module introduction: the complete star schema and conformed dimensions
    2. Anatomy of a star schema
    3. Surrogate keys vs natural keys
    4. Building dim_date: Kiosko's calendar
    5. Conformed dimensions across processes
    6. The bus matrix: mapping Kiosko's processes
    7. Assembling Kiosko's first real star
    8. Mini-project: Kiosko's star schema in DuckDB
  3. 03Star Vs Snowflake Vs One Big Table8 LESSONS
    1. Module introduction: star vs snowflake vs One Big Table
    2. Normalizing a dimension: the snowflake schema
    3. Comparing the cost of a JOIN with EXPLAIN
    4. The wide table (One Big Table) argument
    5. Building Kiosko's sales OBT
    6. When the snowflake still wins
    7. When the OBT still wins
    8. Mini-project: Kiosko's three shapes compared
  4. 04Slowly Changing Dimensions8 LESSONS
    1. Module introduction: when a dimension changes over time
    2. The problem: dim_product isn't static
    3. SCD type 1: overwrite and lose history
    4. SCD type 2: historize with valid_from/valid_to
    5. Implementing SCD type 2 with MERGE INTO
    6. Choosing type 1 vs type 2 per column
    7. SCD type 3 and other variants, briefly
    8. Mini-project: Kiosko's historized dim_product
  5. 05Point In Time Joins And Deduplication8 LESSONS
    1. Module introduction: joining facts against a dimension that has history
    2. Why joining on product_id alone breaks history
    3. The point-in-time join pattern
    4. Late-arriving dimensions
    5. Where duplicate rows come from
    6. Deduplicating with ROW_NUMBER and QUALIFY
    7. Anti-joins to find what changed
    8. Mini-project: Kiosko's correct historical revenue
  6. 06Accumulating And Cumulative Patterns8 LESSONS
    1. Module introduction: two shapes of fact that aren't an order line
    2. The accumulating snapshot fact table
    3. Modeling Kiosko's session funnel
    4. Updating milestones in place
    5. Cumulative table design: the yesterday + today pattern
    6. Rolling windows with array columns
    7. Computing 7- and 30-day actives per store
    8. Mini-project: Kiosko's funnel and cumulative activity
  7. 07Messy Domains And Medallion At Depth8 LESSONS
    1. Module introduction: Kiosko's messy domain, named and under contract
    2. When one fact and two dimensions is not enough
    3. Degenerate dimensions: order_id, in depth
    4. Junk dimensions: bundling low-cardinality flags
    5. Medallion contracts between bronze, silver, and gold
    6. Multiple facts, a single conformed calendar
    7. Schema evolution without breaking gold
    8. Mini-project: Kiosko's multi-fact gold layer
  8. 08Project Kioskos Analytics Warehouse8 LESSONS
    1. Module introduction: the whole guide's capstone
    2. The brief: Kiosko needs a real warehouse, not seven demos
    3. Rebuilding bronze and silver from foundations
    4. Building the star with historized dim_product
    5. Adding the session funnel and cumulative activity
    6. Publishing the OBT mart for the dashboard team
    7. What Kiosko still needs
    8. Mini-project: Kiosko's first analytics warehouse
Reviews

What students say

These reviews are from enrolled students who completed at least 50% of the course. We moderate reviews only on content grounds (spam, offensive language, personal data), never for being critical or negative.

No approved reviews yet.

Be the first to share your experience!

SEC. 06 · THE STUDIO

Why this studio exists

For decades, building software belonged to technical profiles with years of training, and getting a digital product into the real world took companies months or years. No-code and AI have narrowed that gap, but the knowledge is still held by a few.

Tech Benders exists to open that knowledge up, so business teams and non-technical teams can put their ideas into production with the right technical decisions behind them. AI does what you ask of it. Without a technical base, what it builds may not scale with your company’s ecosystem, and its costs can run away over time.

The team knows the pains of large organizations and the speed at which they have to move. It brings solution architecture, data engineering, product built end to end from back end to front end, and daily work with AI. Software that solves what you need in days, not months, with the cost of AI kept in check.

Founders

The studioRead about Tech Benders →

Write to ushi@techbenders.io

Made with Wislab