1

Resolved

New SCD2 (v1.5) upgrading from 1.4

description

You seem to always need to use the New SCD2 (v1.5) for updates that are occurring on a Dimension that has both a SCD1 and SCD2 update, otherwise the SCD2 New records do not come through - this was a fix in v1.5.
 
The NEW SCD2 - Route rows to NEW (behave as 1.4) checkbox - isn't working for SCD1 and SCD2 updates at the same time, or at least this is the bug that is in v1.4 (so still behaving this way) and now fixed in v1.5.

comments

amrit wrote Feb 11, 2010 at 4:57 PM

Although, Delete route into Expired SCD 2 does work as expected

toddmcdermid wrote Feb 12, 2010 at 4:18 AM

I'm afraid I don't understand where the problem is.
Your first paragraph says that you "always need to use the New SCD2" output... and that this was a fix in v1.5 - which I understand means that "it works". Your second paragraph says that choosing to route those rows to "New" (not "New SCD2") isn't working in 1.4, but is fixed in 1.5.
What's broken, exactly?

amrit wrote Feb 12, 2010 at 7:31 PM

Ok, when I clicked "Route rows to NEW (behave as 1.4) checkbox" I expected SCD1 and SCD2 updates to work when being applied at the same time.

For example:

Existing Dimension:
key, ID, numberSCD1, numberSCD2, currentFlag,
1, 1, 1, 1, 1,

Update in Source for both numberSCD1 and numberSCD2 from 1->2, gives the following results - which shows the NEW SCD 2 record is not coming through into the NEW path when both a SCD1 and SCD2 is being performed:

key, ID, numberSCD1, numberSCD2, currentFlag,
1, 1, 1, 1, 0,

So, the bug that is in v1.4 is still present in v1.5 if you re-route the NEW SCD2 into the NEW path.

Hope that makes more sense.

This means you always have to use NEW SCD2 for those updates that consist of both a SCD1 and SCD2 update in the Source.

toddmcdermid wrote Aug 22, 2010 at 2:16 AM

Found this one...

amrit wrote Aug 24, 2010 at 2:56 PM

great, is there a new version coming soon on this?