1

Resolved

Inferred Dimension Members Being Deleted

description

I have a situation that causes some dimension row to arrive quite late. My fact table load handles these situations by loading an inferred member dimension. I have an inferred member identifier that is indicated in the kscd. The problem I am having is that if the dimension load runs after the inferred member row is created before the actual dimension member arrives, the kscd sends the row to the deleted output because there is no match from the source system. Any ideas on how to handle this?

comments

toddmcdermid wrote Feb 9, 2010 at 11:16 PM

Very interesting... for me, I suppose. Let me take a look into that - sure sounds like a bug to me!

balutmaster wrote Feb 9, 2010 at 11:18 PM

I believe I have found the issue - my inferred member indicator is a bit and it looks like the kscd inferred member only supports integer types. I have changed my inferred member to an int and we are in business!

toddmcdermid wrote Feb 9, 2010 at 11:30 PM

I've confirmed this is a bug. The only way you could possibly mitigate it until I fix is by monkeying with the Data Flow outside of the KSCD. Perhaps with a Conditional Split on the Deleted to filter out Inferred members.

toddmcdermid wrote Feb 9, 2010 at 11:31 PM

The Inferred indicator should allow integer and bool types ("bit" is a SQL type)

toddmcdermid wrote Feb 10, 2010 at 4:18 AM

Fixed - updated test harness to ensure it doesn't recur. Thanks for the bug report!