Quantcast
Channel: SCN : All Content - Data Services and Data Quality
Viewing all articles
Browse latest Browse all 4013

Is it correct to assume that the Table Comparison and History Preserving compare column fields are triggers for these transforms to take effect?

$
0
0

First of all I am trying to grasp the concept of Slowly Changing Dimension - Type 2.

 

 

Let us say I have 2 tables namely TBL_SRC_Customer_Info ( source ) and TBL_TGT_Customer_Info ( target ) with Firstname, Lastname, Age, Gender as fields then I added Firstname and Lastname into my table comparison compare column, so for the initial execution I have the following data for both table:

 

ID     Firstname     Lastname     Age     Gender

1      Rod              Castro          21          Male

 

Then I updated my source (I modified the Lastname and age ) into:

 

ID     Firstname     Lastname     Age     Gender

1      Rod              Stewart        20          Male

 

 

Since my Lastname is included in my Table Comparison column compare columns, I am definitely expecting for it to be updated but as for the age I am assuming that it won't because I read that compare columns are the fields that you want "To keep track of [changes]". As far as my aforementioned understanding is concerned, it appears that my Job has an odd behavior so maybe I did something that I wasn't supposed to do. Is this the correct behavior or not? Since Table Comparison modifies the operation code, is the operation code (in my case : update) is applied for the entire row or only for the fields that I specified in the compare columns? Does compare columns acts as triggers to perform an update for the entire row or for only the specified field?

 

Thank you in advance.

 

 

Regards,

Rod Castro


Viewing all articles
Browse latest Browse all 4013

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>