SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Source and Target checksum values are not matching


Source and Target checksum values are not matching

Author
Message
swapnildane
swapnildane
SSC Rookie
SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)

Group: General Forum Members
Points: 35 Visits: 82
Hello,

I found this article really interesting. I implemented this approach using SSIS 2012 in slightly different way. Instead of storing the hash value in target table, I have computed it in the package using another script task and compared this hash value with hash value from source. However, the hash values from source and target are not matching even when there is no change in source data. Not sure why this has happened. I verified that input column sequence is same for both script tasks i.e. I have ticked the inputs columns in same order for source and target script tasks.
I have attached screenshot of the package. Any help is appreciated..!! :-)
Thanks in advance..!!

~
Swapnil


swapnildane
swapnildane
SSC Rookie
SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)

Group: General Forum Members
Points: 35 Visits: 82
Hello,
I found this article really interesting. I implemented this approach using SSIS 2012 in slightly different way. Instead of storing the hash value in target table, I have computed it in the package using another script task and compared this hash value with hash value from source. However, the hash values from source and target are not matching even when there is no change in source data. Not sure why this has happened. I verified that input column sequence is same for both script tasks i.e. I have ticked the inputs columns in same order for source and target script tasks.
I have attached screenshot of the package. Any help is appreciated..!! Smile
Thanks in advance..!!
swapnildane
swapnildane
SSC Rookie
SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)SSC Rookie (35 reputation)

Group: General Forum Members
Points: 35 Visits: 82
I resolved the issue. The script task concatenates the input columns based on order in which they appear in available input column list and not in the order in which they appear in the selected column list So, the order in which we tick available columns to add them to selected columns list is not important :-).
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search