You can use Page Verify option to determine the mechanism used to discover damaged database pages caused by disk I/O path errors. When set to Checksum, a checksum over the contents of the whole page is calculated and the value stored in the page header when a page is written to disk. When the page is later read from disk, the checksum is recomputed and compared to the checksum value stored in the page header. If the values do not match, an error is reported. When set to TornPageDetection, a specific bit for each 512-byte sector in the 8-kilobyte (KB) database page is saved and stored in the database page header when the page is written to disk. When the page is read from disk, the torn bits stored in the page header are compared to the actual page sector information. Unmatched values indicate that only part of the page was written to disk, a condition called a torn page. When set to None, the database will not generate or verify a checksum or torn page detection bits.