jitendra.padhiyar (3/2/2015)
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0xfacb6aaa; actual: 0x9f6b18ec). It occurred during a read of page (1:39510) in database ID 18 at offset 0x000000134ac000 in file.According to me it was Disk I\O error. But what causes it ? What are the other parameters which can corrupt Databases\Tables ? How can we check that ?
Generally speaking, physical corruption can be due to faulting disks or faulting RAM modules.
And last question, how can we prevent such corruption ?
You cannot, but you can check for corruption before taking backups. Here's my script to perform those checks and get an alert in your mailbox if errors are found:
Setting up an e-mail alert for DBCC CHECKDB errors[/url]
-- Gianluca Sartori