Data Warehousing
  • Data Warehousing
  • Readme
  • Fundamentals
    • Terms to Know
    • Jobs
    • Skills needed for DW developer
    • Application Tiers
    • Operational Database
    • What is a Data Warehouse
      • Typical Data Architecture
      • Problem Statement
      • Features of Data Warehouse
      • Need for Data Warehouse
      • Current State of the Art
    • Activities of Data Science
    • Types of Data
    • Data Storage Systems
    • Data Warehouse 1980 - Current
    • Data Warehouse vs Data Mart
    • Data Warehouse Architecture
      • Top-Down Approach
      • Bottom-Up Approach
    • Data Warehouse Characteristic
      • Subject Oriented
      • Integrated
      • Time Variant
      • Non Volatile
    • Tools
    • Cloud vs On-Premise
    • Steps to design a Data Warehouse
      • Gather Requirements
      • Environment
      • Data Modeling
      • Choosing ETL / ELT Solution
      • Online Analytic Processing
      • Front End
      • Query Optimization
    • Dataset Examples
    • Thoughts on some data
  • RDBMS
    • Data Model
      • Entity Relationship Model
      • Attributes
      • Keys
      • Transaction
      • ACID
    • Online vs Batch
    • DSL vs GPL
    • Connect to Elvis
    • SQL Concepts
      • Basic Select - 1
      • Basic Select - 2
      • UNION Operators
      • Wild Cards & Distinct
      • Group By & Having
      • Sub Queries
      • Derived Tables
      • Views
    • Practice using SQLBolt
  • Cloud
    • Overview
    • Types of Cloud Services
    • Challenges of Cloud Computing
    • AWS
      • AWS Global Infrastructure
      • EC2
      • S3
      • IAM
    • Terraform
  • Spark - Databricks
    • Storage Formats
    • File Formats
    • Medallion Architecture
    • Delta
  • Data Warehousing Concepts
    • Dimensional Modelling
      • Star Schema
      • Galaxy Schema
      • Snowflake Schema
      • Starflake Schema
      • Star vs Snowflake
      • GRAIN
      • Multi-Fact Star Schema
      • Vertabelo Tool
    • Dimension - Fact
    • Sample Excercise
    • Keys
      • Why Surrogate Keys are Important
    • More Examples
    • Master Data Management
    • Steps of Dimensional Modeling
    • Types of Dimensions
      • Date Dimension Table
      • Degenerate Dimension
      • Junk Dimension
      • Static Dimension
      • Conformed Dimensions
      • Slowly Changing Dimensions
        • SCD - Type 0
        • SCD - Type 1
        • SCD - Type 2
        • SCD - Type 3
        • SCD - Type 4
        • SCD - Type 6
        • SCD - Type 5 - Fun Fact
      • Role Playing Dimension
      • Conformed vs Role Playing
      • Shrunken Dimension
      • Swappable Dimension
      • Step Dimension
    • Types of Facts
      • Factless Fact Table
      • Transaction Fact
      • Periodic Fact
      • Accumulating Snapshot Fact Table
      • Transaction vs Periodic vs Accumulating
      • Additive, Semi-Additive, Non-Additive
      • Periodic Snapshot vs Additive
      • Conformed Fact
    • Sample Data Architecture Diagram
    • Data Pipeline Models
    • New DW Concepts
Powered by GitBook
On this page
  • Uses of using Degenerate Dimension Table
  • Other Examples of Degenerate Dimensions are
  1. Data Warehousing Concepts
  2. Types of Dimensions

Degenerate Dimension

PreviousDate Dimension TableNextJunk Dimension

Last updated 1 year ago

Generally, what is a Dimension table? Something like a master list. Employee, Product, Date, Store.

In a data warehouse, a degenerate dimension is a dimension key in the fact table that does not have its dimension table.

It is key in the fact table but does not have its dimension table.

Degenerate dimensions are most familiar with the transaction and accumulating snapshot fact tables.

Means no separate Dimension table.

OrderNo is degenerate dimension. As it has no Dimension table.

Uses of using Degenerate Dimension Table

- Grouping line items
- Getting the average sale
- Tracking

Other Examples of Degenerate Dimensions are

  1. Order number or invoice number: This is a typical example of a degenerate dimension. It is a unique identifier for an order or an invoice but has no meaningful attributes other than its value. This degenerate dimension can be used in a fact table to analyze sales by order or invoice number.

  2. Tracking number: Another example of a degenerate dimension is a tracking number for a shipment. Like an order number, it is a unique identifier but has no additional attributes associated with it. It can be used in a fact table to analyze shipping performance or delivery times.

  3. ATM transaction number: In banking, an ATM transaction number is a unique identifier for a transaction at an ATM. It can be used in a fact table to analyze ATM usage patterns and trends.

  4. Serial number: A serial number is a unique identifier assigned to a product or equipment. It can be used in a fact table to analyze the performance of a particular product or equipment.

  5. Coupon code: A coupon code is a unique identifier to redeem a discount or promotion. It can be used in a fact table to analyze the usage and effectiveness of different marketing campaigns or promotions.

Degenerate dimensions are helpful when we have a unique identifier for an event or transaction. Still, it has no additional attributes that make it sound like a separate dimension table. In these cases, we can include the unique identifier in the fact table as a degenerate dimension.