Validating data transmissions start your own dating service
Figure 2 shows an example of a file that was corrupted when it was transferred using the operating system.
This image was fine on the media card, but became corrupted when it was copied to a hard drive with a bad bridge board. The bad bridge board in the drive enclosure was eventually diagnosed because validated transfers kept flagging transfer errors.
When binary checksums are used, 32-bit redundancy check (CRC) occurs on a column-by-column basis rather than a CRC on the physical row on the data page.
This allows the columns with the table to be in any order physically on the data page, but still compute to the same CRC for the row.
The best way to prevent transfer errors is to use validated transfers whenever you copy files from one storage media to another.
One of the most useful tools in data validation is the open-source MD-5 checksum (or MD-5 hash).Specify one of the following validation types and the Distribution Agent or Merge Agent will validate data the next time it runs: When validation is complete, the Distribution Agent or Merge Agent logs messages regarding success or failure (replication does not report which rows failed).These messages can be viewed in SQL Server Management Studio, Replication Monitor, and replication system tables.For digital photographers, data validation generally addresses three questions. There's simply no way to know if the collection is complete without having some kind of record of what is supposed to be there. Proper data validation can spot problems early, before they lead to loss of your image files. This is probably the easiest validation to do, at least for people with a reasonably organized collection.