Hi,
Company wants to enforce data movement controls. When data moves from provisioning database to consuming Application, we need to ensure the data moved from source to destination without data loss or corruption. For that, they want the count of rows, hash on a column on the source side to match the count of rows,hash on a column on the destination(consuming application database). While the standard could be applied well when data movement is through files, when we move data from one database to another using simple query or ETLs like SSIS, we are challenged to find a simple way to exchange the count and hash.First of all do you think, a movement control like this is necessary or best practice when we use .NET Code/Java code to connect to the source database and extract the data and update the target database? Do we anticipate data to get lost ? Also as an extension of the standard,
Much appreciate for any help/suggestion .