Thoughts on intra-day changes on SCD2 dimensions

Topics: Issues 2: Using the Component (Design-Time), Possible Bugs/Missing Features?
Jan 10, 2013 at 6:31 PM

I have cases where it is quite valid to have multiple changes to a source system record on any given day. I am lucky (or unlucky, depending on how you look at it) to receive each version as a separate row which includes a sequence number and an unreliable timestamp (they may not be unique). The sequence number is not part of the business key (nor should it be because it represents history, not identity) so obviously the component throws a

Warning: Duplicate Business Key 'xxxxxxx' read from Source_System input.

and sends the row to the Invalid Input output.


In this case its expected and the expectation is to have each update processed and new SCD2 rows generated with all but the last one expired. Any thoughts on this behavior in relation to DMSCD in terms of new features or work-around?