03-fact-table-patterns

Classify measures and design advanced fact table patterns for Gold layer modeling.

1|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/prashsub/vibe_coding_lakehouse_starter_repo --skill 03-fact-table-patterns-prashsub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 03-fact-table-patterns
Source: https://github.com/prashsub/vibe_coding_lakehouse_starter_repo/tree/main/data_product_accelerator/skills/gold/design-workers/03-fact-table-patterns
Command: npx skills add https://github.com/prashsub/vibe_coding_lakehouse_starter_repo --skill 03-fact-table-patterns-prashsub

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the complexities of designing fact tables beyond basic patterns, ensuring accurate data aggregation and analysis by classifying measures and handling intricate business scenarios.

Core Features & Use Cases

  • Measure Additivity Classification: Distinguish between additive, semi-additive, and non-additive measures to prevent incorrect dashboard calculations.
  • Advanced Fact Patterns: Implement factless fact tables, accumulating snapshots, consolidated facts, and header/line patterns for specialized modeling needs.
  • Late-Arriving Data Handling: Design strategies for incorporating facts and dimensions that arrive after their intended reporting period.
  • Use Case: When designing a data model for an e-commerce platform, use this Skill to correctly model sales revenue (additive), inventory levels (semi-additive), and unit prices (non-additive), and to handle scenarios where product information might arrive after a sale is recorded.

Quick Start

Use the 03-fact-table-patterns skill to classify measures as additive, semi-additive, or non-additive for the fact_sales table.

Frequently Asked Questions about 03-fact-table-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I classify measure additivity for fact tables in dimensional modeling?

Measure additivity classifies fact table measures as additive, semi-additive, or non-additive to prevent incorrect dashboard calculations. You distinguish between measures that sum across all dimensions, specific dimensions only, or require complex aggregation.

When do I need an accumulating snapshot fact table?

An accumulating snapshot fact table is needed when modeling processes with defined milestones, like order fulfillment. It updates a single row over time as events occur, contrasting with transactional patterns that add new rows for each event.

What is the best way to handle late-arriving facts and dimensions in a data warehouse?

Handling late-arriving facts and dimensions requires specific Gold layer design strategies to incorporate data arriving after its intended reporting period. You design patterns that correctly update historical aggregates without corrupting existing reporting periods.

How do I model factless fact tables for business events?

Factless fact tables record business events or coverage without numeric measures. You use them to track event occurrences, such as student attendance or product promotions, enabling analysis of activity frequency and relationships between dimensions.

What are the limitations of consolidated fact table patterns?

Consolidated fact tables combine multiple business processes into a single table, limiting granular analysis per process. You should evaluate whether the query performance benefits outweigh the potential risks of mixing grain and complicating measure additivity.