Hi all!

Thx for your answeres. I think this behavior of the SCD is a bug.

The idea of moving all duplicates to a new table and import them afterwards would be...

Hi!

The import files represent the change history of an item. Generally the last line of an item (same PK) in the file should contain the actual version of the dataset.

So...

Hi!

Unfortunately I need to import both rows... Is there a way to tell teh Slowly Changing Dimension to complete the transaction and open the table again after each row?

Günther

great minds think alike 😉

I solved this one 😉

An UPDATE does not spawn en error if no line is changed. I just had to check

IF @@ROWCOUNT = 0

/lackyg

Thank you!

It is a good idea to let the SQL server handle this problem.

best regards

/gü

Thank you very much for you help!