Kimball Forum
Would you like to react to this message? Create an account in a few clicks or log in to continue.

Much ado about overlapping type 2 change

Go down

Much ado about overlapping type 2 change Empty Much ado about overlapping type 2 change

Post  cjrinpdx Wed Aug 31, 2011 1:01 pm

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)

cjrinpdx

Posts : 51
Join date : 2011-07-14
Location : Portland, OR

Back to top Go down

Much ado about overlapping type 2 change Empty Re: Much ado about overlapping type 2 change

Post  ngalemmo Wed Aug 31, 2011 2:24 pm

Option 1. Its a change. It doesn't matter what it is being changed to. The process is always the same.
ngalemmo
ngalemmo

Posts : 3000
Join date : 2009-05-15
Location : Los Angeles

http://aginity.com

Back to top Go down

Back to top


 
Permissions in this forum:
You cannot reply to topics in this forum