Post reply

Source and Target checksum values are not matching

  • October 8, 2013 at 8:23 am

    #277883

    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

  • October 8, 2013 at 8:25 am

    #1656762

    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..!!

  • October 15, 2013 at 11:20 pm

    #1658791

    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 :-).

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply