July 25, 2019 at 3:11 pm
I would like to know , just in case CHECKDB maintenance job is running for 4 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? I know it's not a recommended and good practice. 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.
The reason i want to kill is because there is another job running causing the log to grow and it can fill the disk space and cause the job not to finish.
Thanks in advance.
July 25, 2019 at 6:14 pm
It really depends on the progress of the checkdb when you kill it. Nothing may happen and everything seems fine or it could look like it's hanging. If it appears to hang, it's generally due to the internal snapshot. There is an explanation of this in this blog:
The Curious Case of… unstoppable DBCC CHECKDB
Sue
July 26, 2019 at 2:43 pm
Thanks Sue! I didn't kill the process but below error is what i am seeing in the log.Does it mean someone killed the session or it is interrupted by other process cause the job to fail. Please advise?
Cannot continue the execution because the session is in the kill state.
July 26, 2019 at 4:37 pm
You'd need to do more digging to know for sure. If the job failed, you would want to look at why the job failed and check the error logs for more information on the job failure as well as any logged kill commands and any details from the job history. What you are seeing could have even been from a failover while the checkdb was executing.
Sue
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply