Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Torn_page_detection Vs Checksum (SQL Server 2005 database upgrade) Expand / Collapse
Author
Message
Posted Wednesday, July 1, 2009 10:00 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Friday, July 11, 2014 8:22 AM
Points: 742, Visits: 1,053
Hi masters,

I have a database in SQL Server 2000 that i'm converting (upgrading) to 2005.

When i make the restore from the SQL Server 2000 in the SQL Server 2005, this database is still with the option of torn_page_detection on, and the checksum option is set to false.

I'm thinking in changing the option from torn_page_detection to checksum, what do you think? I read that is more secure. Will i have any problems with my existing applications? what do you masters do in this case?


thank you,

Pedro
Post #745564
Posted Wednesday, July 1, 2009 10:54 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 4:03 PM
Points: 42,485, Visits: 35,554
It's not about security. Checksum page protection lets SQL pick up more forms of corruption than Torn page could, and also can show that said corruption is caused outside of SQL.

There's a very small overhead in having it on, I think it's around a 2% hit. Personally I'd say that every SQL 2005+ database should have page protection set to checksum.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #745619
Posted Wednesday, July 1, 2009 2:10 PM
SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: 2 days ago @ 1:03 PM
Points: 4,388, Visits: 9,510
In addition to what Gail has stated, the default for new databases in 2005 is CHECKSUM.

Jeffrey Williams
Problems are opportunites brilliantly disguised as insurmountable obstacles.

How to post questions to get better answers faster
Managing Transaction Logs
Post #745740
Posted Tuesday, July 20, 2010 1:54 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, April 14, 2011 11:53 AM
Points: 40, Visits: 68
check the SSC headline from today, there is a good explanation on this topic
Post #955337
Posted Tuesday, July 20, 2010 2:16 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 4:03 PM
Points: 42,485, Visits: 35,554
Please note: 18 month old thread.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #955356
Posted Tuesday, July 20, 2010 2:33 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, April 14, 2011 11:53 AM
Points: 40, Visits: 68
oops sorry, I was mislead by related posts to this morning article, I did not notice the post date.
Post #955367
Posted Wednesday, July 21, 2010 6:08 AM
SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Thursday, May 1, 2014 8:37 AM
Points: 4,716, Visits: 208
I always wondered why the newsletter puts articles that old in it?
Post #956278
Posted Wednesday, July 21, 2010 6:13 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 4:03 PM
Points: 42,485, Visits: 35,554
Twinsoft SME (7/21/2010)
I always wondered why the newsletter puts articles that old in it?


Newsletter only shows forum posts with recent activity. kagemaru found this via the 'related content' (sidebar) in an article. Once he posted, the thread had recent activity and appeared in the newsletter.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #956281
Posted Friday, November 18, 2011 5:05 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, June 11, 2013 5:09 AM
Points: 14, Visits: 77
I've just come across this post, whilst investigating a similar situation (though legacy).

Can anyone explain what potential issues there are (if any) in changing a production database from TORN_PAGE_DETECTION to CHECKSUM?

Am I right in assuming that CHECKSUM can't be implemented retrospectively anyhow, and so it will only affect new pages, and therefore that I am safe to make this change?

Thanks

Andy
Post #1208242
Posted Friday, November 18, 2011 6:38 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Yesterday @ 4:03 PM
Points: 42,485, Visits: 35,554
None whatsoever.

It will be applied to pages the next time they are written to (not read). That's old pages and new.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1208314
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse