DSXchange

This is a known bug to IBM. The fix for it will be available in 8.0.1.1 in the mid to end of Sept. 2007. For now - if you have any nulls in either your source or dimension which need to be type1 or type2 ... it won't work.

Just for kicks, I modified my SQL (for the source) so that there was a non-null value for each record coming accross. First run - everything is fine Second run - if some of the date values have been modified, I get the following on the output to the SCD ... the one that updates the dimension: Update...

Yes the field does change. I also have a EDW_CREATION_DATE and EDW_DISABLE_DATE that behave like the field you are referencing ... and I'm using the Effective Date (Type 2) and Expiration Date (Type 2) purpose for these fields.

Hi, I am using the SCD stage to update a dimension. I have a date field (active_start_date) which I have defined as a type 2 field. Most of the time, this field is null. My columns going into and out of the SCD stage allow nulls. I beleive what is happening is that DS is trying to compare a NULL val...