Much ado about overlapping type 2 change

[cjrinpdx]

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)

[ngalemmo]

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