Handling SCD1 and SCD2 changes on the same record at the same time

Nov 19, 2009 at 10:42 PM

Greetings,

Thanks for developing this component, I am really liking it so far. In testing it today however, I noticed some strange behavior that I cannot figure out. I have the following definition for my existing dimension SCD usage.

UserKey (Surrogate Key)
UserID (Business Key)
FirstName (SCD1)
LastName (SCD1)
ManagerID(SCD2)
EffectiveDtm (SCD2 Effective Date)
ExpirationDtm (SCD2 Expiry Date)

In my testing I changed the FirstName and the ManagerID in the source, executed the package, and this is where my issue is:

Run 1

  • 1 row sent to Updated SCD1 output
  • 0 rows sent to any other output (besides auditing)

Run 2

  • 1 row sent to New output
  • 1 row sent to Expired SCD2 output

This appears to me that the SCD1 changes override the SCD2 changes. Here is what I expected to see:

Run 1

  • 1 row sent to Updated SCD1 output
  • 1 row sent to New output
  • 1 row sent to Expired SCD2 output

Is there a setting somewhere that sets the precedence or ...?

Thanks,
Ben

Coordinator
Nov 30, 2009 at 12:51 PM

You may be running into issue 3887.