We've been having sporadic cases of corruption. The tables vary but the message is consistent:Msg 605, Level 21, State 3, Line 1
Attempt to fetch logical page (5:537) in database 47 failed. It belongs to allocation unit 72057602025521152 not to 72057602063532032.
When I inspect the tables using DBCC IND and DBCC PAGE I can see that, for example, page 5:537 does have an incorrect allocation unit in it's header (as compared to the IAM page).
Yes, most sources state that most corruption is caused by I/O sub-system, but in our situation we need to prove this.
On this ms page http://support.microsoft.com/kb/2015739
Ensure you have the PAGE_VERIFY=CHECKSUM database option turned on. While it is possible to still encounter a Msg 605 error with checksum enabled (Ex. "scribbler" problem or incorrect page provided from I/O system), enabling checksum can provide definitive proof that the page was modified incorrectly within the I/O system.
Could anyone explain to me how this provides definitive proof? Definitive proof would be very helpful in our case!