Component finds SCD2 changes when there are none

Topics: Issues 3: Executing the Component (Run-Time)
Nov 28, 2012 at 7:03 AM


I'm currently using the dimension merge SCD component to finish a proof of concept Setup.

I am running this against a firebird database as "original" table and a MSSQL Dimension Table.

The first run, when the Dimension table is empty, works like expected.

When i run the component a second time - with unchanged original table - the component starts to act strange:

It detects changes in a column that definitively did not Change (same unchanged database, no Triggers attached.. ) and spews out a lot of Messages in the form of

"Duplicate Business Key 'XXXX0000' read from Existing_Dimension Input."

Is this something sb can spot on the fly-by or do you need more data to tell?

Thanks in advance