Much ado about overlapping type 2 change
2 posters
Page 1 of 1
Much ado about overlapping type 2 change
Let's say we have an employee dimension with a last name attribute. Last name is a type 2.
The employee gets married, triggering a type 2 change (last name) and creates a new record.
Let's say the same employee gets divorced (sorry), triggering a type 2 change (last name changes back to maiden name).
What should we do?
1) Trigger another type 2 change, and create a new record.
2) Reactivate the old record (change RowIsCurrent = True)
The employee gets married, triggering a type 2 change (last name) and creates a new record.
Let's say the same employee gets divorced (sorry), triggering a type 2 change (last name changes back to maiden name).
What should we do?
1) Trigger another type 2 change, and create a new record.
2) Reactivate the old record (change RowIsCurrent = True)
cjrinpdx- Posts : 51
Join date : 2011-07-14
Location : Portland, OR
Re: Much ado about overlapping type 2 change
Option 1. Its a change. It doesn't matter what it is being changed to. The process is always the same.
![-](https://2img.net/i/empty.gif)
» SCD Type 2 Change Reasons
» Type 2 Change Handling
» Handling a SCD Type 2 change in a fact
» SCD2 Type Change Question
» Handling a correction vs a change in SCD type II dimension.
» Type 2 Change Handling
» Handling a SCD Type 2 change in a fact
» SCD2 Type Change Question
» Handling a correction vs a change in SCD type II dimension.
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
|
|