Have you enabled page verification for your database? I have a monitoring system for SQL that is telling me I should enable this to prevent corruption of the db. This is the description:
For best practice, some form of page verification should be turned on for all production and system databases. The act of page verification incurs minimal overhead, and the benefit of helping to identify corrupt data is worth the extra overhead.
Between the time SQL Server writes a page to disk, then later reads the same page, it is possible that the data stored in the page may get corrupted due to circumstances outside the control of SQL Server. It is a rare occurrence, but when it does occur it can be devastating to a database, often requiring that the entire database be restored. While SQL Server cannot prevent corruption outside its control, it does at least have the ability to identify corrupt data. While this won't prevent or fix the problem, it can make the DBA aware of the problem so that it can be addressed as quickly as possible.
Ours is set to CHECKSUM. If your SQL server doesn't have any I/O bottleneck issues, CHECKSUM is typically the better option, as it provides better corruption prevention than TORN_PAGE_DETECTION.
Here's a good article on the matter:
http://www.red-gate.com/supportcenter/content/SQL_Response/help/1.3/SR_pageverification
Hope that helps, Jeff