torn page detection vs checksum

can anyone provide a management freindly low tech summary of what the risks are in not using CHECKSUM and using torn page detection for "page verifacation".

What exactly is "page verifacation".

And what exactly are either checking/detecting for? Why is one considered better than the other?

Some of the links I have read have confused me even further so some comments much more preferable.
LVL 3
pma111Asked:
Who is Participating?
 
KimputerCommented:
Did you read the official page though:

http://technet.microsoft.com/en-us/library/aa337525(v=sql.105).aspx

Checksums were added later (torn in SQL 2000 vs checsum in SQL 2005). That's for a reason!
Torn page works like this, write page after page after page after each page, write the bits you need. You can still write every page TOTALLY wrong though, and then still add the bits you need. If you check the torn page bits, you would think your database is in tip top shape.
Checksum writes a checksum of the total page at the end. If you check it later, if any error occured you can easily tell it. Obviously requires more CPU, but 5 years had past, so they didn't mind it to add it as a feature.

Therefore, if you want to be sure, checksum. If you have REALLY old and slow hardware, maybe step back to torn page.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.