EDITable
  • Introduction to EDITable
    • Why EDITable?
    • Supported Database Connections
  • Get Started
    • EDITable Pre-requisites
      • Admin consent for EDITable's Entra ID
        • Basic consent
        • Full admin consent
    • Install EDITable
    • Add EDITable visual
  • Getting Data into EDITable
    • Connect to Data
      • Get data
      • Assign fields
      • Configuration Steps
        • Configure source
        • Configure Columns
        • Configure Type 2 SCDs (Optional)
    • Create a Table
      • Create From Scratch
      • Use Existing Table
      • Import Data
  • Working with EDITable
    • EDITable interface
    • Manage Columns
      • General
      • Constraints
      • Lookup and Relation
      • Display
      • Import/Export Configuration
      • Add Database Column
      • Insert Column
    • Column Access Control
    • Row Identification
    • Table Operations (Insert/Update/Delete)
      • Edit data
      • Bulk Edit
      • Find and Replace
      • Insert rows
      • Insert Column
      • Import rows
      • Delete rows
      • Duplicate rows
      • Copy rows
      • Preview Changes
      • Reset Changes
    • Explore data
      • Search and filter
      • Sort and reorder
      • Show/Hide columns
      • Pin columns
      • Group Rows By
      • Summarize Column
    • Basic formatting
    • Conditional Formatting
  • Row Access Control
  • Approval Workflow
    • Review Changes - Workflow process
  • Type 2 SCDs
    • Configuring Type 2 SCDs in EDITable
  • Audit logs
  • Webhook
  • Display Settings
  • Commenting and Collaboration
    • Assign users & task status
    • View all comments & track changes
    • Comment Settings
  • Admin Portal & EDITable Console
    • Tables
    • Transaction Logs
    • Insights (Metrics)
    • Utility
      • Download Report
      • Pipeline
        • Power BI & EDITable deployment pipelines
        • Deployment in different destinations
        • Trigger deployment pipeline from external applications
        • Logs & other pipeline options
    • Manage Profile
    • Admin Portal
      • User Management
      • Settings
        • General Settings
        • Writeback Settings
          • Settings
          • EDITable managed DB
        • API token
    • Onboarding Actions
  • Formula and Functions
    • Conditional statements
      • IF
      • IFNA
      • SWITCH
    • Logical functions
      • AND
      • IN
      • ISBLANK
      • ISEMPTY
      • ISNUMBER
      • NOT
      • OR
      • XOR
    • Math functions
      • ABS
      • AVERAGE
      • AVERAGEIF
      • AVERAGEEXNEG
      • AVERAGEEXZERO
      • AVERAGEEXZERONEG
      • CEILING
      • COUNT
      • COUNTIF
      • DIVIDE
      • EVEN
      • EXP
      • FLOOR
      • LOG
      • MAX
      • MIN
      • PCT
      • POWER
    • Text formatting functions
    • Date functions
      • DATE
      • DATE.FORMAT
    • Other operators
  • Keyboard Shortcuts
  • Release Notes
    • EDITable - v1.7.5
    • EDITable - v1.7
    • EDITable - v1.6.5
    • EDITable - v1.6
Powered by GitBook
On this page
  • 1. Understanding Type 2 SCDs
  • 2. Example for Type 2 SCDs

Type 2 SCDs

PreviousReview Changes - Workflow processNextConfiguring Type 2 SCDs in EDITable

Last updated 4 months ago

Type 2 Slowly Changing Dimension (SCD) is a data warehousing method used to track changes in data over time by preserving the change history. You can view the historical data for each record and their corresponding time range when it was valid.

If you're already familiar with SCDs, you may skip this section and move ahead to the

1. Understanding Type 2 SCDs

  • Whenever an entity's data in any dimension changes, a new row is created instead of overwriting the old ones.

  • Each new row includes the updated information along with the start date and end date that indicate the validity period of the updated information.

  • There is an additional flag column that indicates the record that is currently active. This column can be of the checkbox type or a simple true/false or 0/1 column.

  • There can be one or more timestamp columns in addition to the start date to signify when a new record was actually created or when the change was made effective.

This approach allows us to analyze the historical data and understand how the information has evolved over time.

2. Example for Type 2 SCDs

Let us consider an employee database where the employees' details, such as salary, incentive, job role, etc., can slowly change over time.

With SCDs, whenever there is a change, a new row with the updated details is created instead of overwriting the old one. This new row includes an effective start date that indicates when it was updated, or when the new details became live.

Meanwhile, the old row will have an end date marking when it was last valid. Likewise, every change made to an employee is tracked through a series of rows, each with its respective start and end dates.

Find below the database where SCDs are in place:

ID (Surrogate Key)
Emp.ID (Business Key)
Employee Name
Salary
RowValidFrom
RowValidTo

1

C501

John S

70000

20-10-2023

23-10-2024

56

C002

Alan B

75000

01-01-2024

31-12-2025

234

C501

John S

80000

24-10-2024

31-12-2025

235

C988

Lily S

65000

21-10-2024

31-12-2025

One table row represents an entity's attributes for a defined timespan. The whole lifespan of one business entity can be inferred from a list of such rows.

In the next section, we will discuss how to configure a database that can support SCDs and how you can assign the appropriate keys in EDITable.

next section.