I've run sp_blitz (version 45) on our test database server.
It complains about
Database [MDS] has TORN_PAGE_DETECTION for page verification. SQL Server may have a harder time recognizing and recovering from storage corruption. Consider using CHECKSUM instead.
But this is a database from Microsoft.
Is it wise to change the Page Verification to CheckSum?
Or should we wait for Microsoft to release a new version of MDS?
Best Answer
I would suggest you follow what the
sp_blitz
recommended. You can change the option toCHEKSUM
. Checksum might be able to detect more problem that torn_page.Torn page allows you to detect whether page was successfully written to disk or not. It would not check what is inconsistency inside the page. While checksum performs more thorough checks. Having said all this you must know
there is no replacement of good backup and you must (if possible) run dbcc checkdb every day
.What Paul said, quoting from This SQLServercentral link
Following is what BOL document has to say
NOTE: If you enable page checksum it would not be enabled for entire pages of the databases. There is no process as such which puts this option for all pages. When a certain page would be
read in memory, changed, and written back
to disk checksum would then be enabled for that page. So you would have to perform operation like index rebuild to bring as much page as possible in memory. Paul Randal has Myth section related to Checksum please read it. Databases that are created on SQL Server 2005 and 2008 will have page checksums enabled automatically unless user changes the setting in the model database.