October 30, 2013 at 3:36 pm
Hi all,
I just want a confirmation, i was told that running checkdb on a db that has not had checkdb run in sometime, can cause problems if corruption is found. Is this true?
Some of our DB's, integrity checks are not done on a regular basis and i want to perform integrity checks on a daily basis.
October 30, 2013 at 3:44 pm
Ask yourself, which is preferable, a corrupt database that you know is corrupt or a corrupt database that you don't know is corrupt.
CheckDB when run without a repair option (which is how you should run it) reads and checks for corruption, that's it.
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
October 30, 2013 at 3:54 pm
Thank you Gail for the prompt response.
I understand what you mean regarding a corrupt DB. I would prefer to know if a Db is corrupt than not know.
GilaMonster (10/30/2013)
CheckDB when run without a repair option (which is how you should run it) reads and checks for corruption, that's it.
My thoughts exactly, appreciate the feedback, and i will definitely be taking this up with my senior.
Thank you again Gail.
November 12, 2013 at 9:53 am
If this is a particularly busy system, I'd consider restoring a recent backup onto another server and run CHECKDB against that.
It can be a pretty intensive taskand may impact system performance.
March 11, 2014 at 2:33 pm
Before proceeding with this make sure you have abundant information regarding checkdb as it comes with useful switches which can significantly cause server stress .
Go step by step for starters read this : http://www.sqlperformance.com/2012/11/io-subsystem/minimize-impact-of-checkdb
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply