July 1, 2009 at 10:00 am
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
July 1, 2009 at 10:54 am
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, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 1, 2009 at 2:10 pm
In addition to what Gail has stated, the default for new databases in 2005 is CHECKSUM.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
July 20, 2010 at 1:54 am
check the SSC headline from today, there is a good explanation on this topic
July 20, 2010 at 2:16 am
Please note: 18 month old thread.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 20, 2010 at 2:33 am
oops sorry, I was mislead by related posts to this morning article, I did not notice the post date.
July 21, 2010 at 6:08 am
I always wondered why the newsletter puts articles that old in it?
July 21, 2010 at 6:13 am
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, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 18, 2011 at 5:05 am
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
November 18, 2011 at 6:38 am
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, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 18, 2011 at 6:41 am
Great thanks very much!
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply