<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2005
»
Administering
»
Torn_page_detection Vs Checksum (SQL Server...
11 posts, Page 1 of 2
1
2
»»
Torn_page_detection Vs Checksum (SQL Server 2005 database upgrade)
Rate Topic
Display Mode
Topic Options
Author
Message
river1
river1
Posted Wednesday, July 01, 2009 10:00 AM
Say Hey Kid
Group: General Forum Members
Last Login: Tuesday, May 07, 2013 6:56 AM
Points: 679,
Visits: 953
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
GilaMonster
GilaMonster
Posted Wednesday, July 01, 2009 10:54 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 12:38 AM
Points: 37,725,
Visits: 29,981
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
Jeffrey Williams 3188
Jeffrey Williams 3188
Posted Wednesday, July 01, 2009 2:10 PM
SSCarpal Tunnel
Group: General Forum Members
Last Login: Friday, May 17, 2013 11:21 AM
Points: 4,317,
Visits: 9,216
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
kagemaru
kagemaru
Posted Tuesday, July 20, 2010 1:54 AM
SSC Rookie
Group: General Forum Members
Last Login: Thursday, April 14, 2011 11:53 AM
Points: 39,
Visits: 68
check the SSC headline from today, there is a good explanation on this topic
Post #955337
GilaMonster
GilaMonster
Posted Tuesday, July 20, 2010 2:16 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 12:38 AM
Points: 37,725,
Visits: 29,981
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
kagemaru
kagemaru
Posted Tuesday, July 20, 2010 2:33 AM
SSC Rookie
Group: General Forum Members
Last Login: Thursday, April 14, 2011 11:53 AM
Points: 39,
Visits: 68
oops sorry, I was mislead by related posts to this morning article, I did not notice the post date.
Post #955367
Rick.Cornell.SME
Rick.Cornell.SME
Posted Wednesday, July 21, 2010 6:08 AM
SSCarpal Tunnel
Group: General Forum Members
Last Login: Saturday, March 24, 2012 3:31 PM
Points: 4,232,
Visits: 207
I always wondered why the newsletter puts articles that old in it?
Post #956278
GilaMonster
GilaMonster
Posted Wednesday, July 21, 2010 6:13 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 12:38 AM
Points: 37,725,
Visits: 29,981
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
Andy Siantonas
Andy Siantonas
Posted Friday, November 18, 2011 5:05 AM
Grasshopper
Group: General Forum Members
Last Login: Wednesday, May 01, 2013 12:20 PM
Points: 14,
Visits: 76
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
GilaMonster
GilaMonster
Posted Friday, November 18, 2011 6:38 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 12:38 AM
Points: 37,725,
Visits: 29,981
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 »
11 posts, Page 1 of 2
1
2
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
