May 21, 2014 at 4:50 am
Hi,
I would like to know , just in case CHECKDB maintenance job is running for 5 hours and admin chosen to kill that operation.
Usually the job takes not more than 2 hrs.
What can happen if CHECKDB is killed in the middle of process?
What are steps to be taken care even before thinking of killing CHECKDB operation ?
Did anyone faced this situation any time? if so, please do share on how to handle such situation.
Thanks in advance.
May 21, 2014 at 4:57 am
Oracle_91 (5/21/2014)
What can happen if CHECKDB is killed in the middle of process?
The CheckDB operation stops.
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
May 21, 2014 at 5:29 am
Is there anything happens internally because even the KILL takes a long time.
May 21, 2014 at 5:34 am
No.
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
May 21, 2014 at 5:39 am
Thank you Gail. Again, in the fist place , is it perfectly safe to KILL checkdb operation if required?
May 21, 2014 at 6:11 am
It's perfectly safe to kill anything (well, unless your developers have written procedures which don't use transactions, but that's not a SQL internals problem)
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
May 21, 2014 at 6:15 am
Thank you 🙂
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply