Orion database setting: Page Verify Recovery type: Checksum vs Torn Page Detection

Question

Hi guys,

I noticed recently that not all our Orion databases are configured equally. Specifically when reviewing the Page Verify type.

Some databases have this set to CHEKCSUM while others have it set to TORN_PAGE_DETECTION

I know for a fact that this type of setting is NOT modified on our databases. The question is, however, why are they different?

There isn't any logic as to why it would be set one way or the other.

All databases have NPM and NCM. Some have SAM and a few other modules. The databases have been created at various points in time by the application and not manually.

Could this be something related to when and what version of NPM was initially deployed? Or could it perhaps be related to RC software being used in an update at some point?

I would really like to have an explanation for this and also whether or not it would be safe to change it - if so, what would be the correct procedure.

Usually CHECKSUM is the default and preferred type, even through Torn_Page_Detection might have benefits.

sqlrockstar​ or a dev ?

aLTeReGo · Answer

Yes, I would recommend switching them to CHECKSUM.

Deltona · Answer

Thanks for the explanation. The oldest database from the bunch is from 2008 which was initially deployed in express but the page verify on that one is checksum

Either way, would it be advisable to change the ones set to torn back to checksum?

sqlrockstar · Answer

The only possible explanation I have to offer is that your database was created prior to SQL 2005, upgraded to a more recent version at some point, and that option was left alone. My understanding is that since 2005 onwards, the default is CHECKSUM, unless you override, and there is no reason to override that setting. HTH