1

I killed DBCC CheckDB Job of 3TB Database which has been rolling back since 17 hours with 89 %.as i have checked that the SPID running with waittype EXECSYNC. Could we have any other way to clear this mess without restarting SQL Server

5
  • 2
    Oh dear. Why did you kill it?
    – Philᵀᴹ
    Oct 20, 2019 at 12:28
  • Developer was requested for kill this process, so I did it Oct 20, 2019 at 12:31
  • 1
    Why do you think a restart will fix your “issue”?
    – S3S
    Oct 21, 2019 at 2:27
  • RE:VTC, not sure how this is off-topic, voting to leave open Oct 21, 2019 at 11:38
  • Unfortunately I have restarted sql services and luckily nothing bad happened, server and databases are healthy and online ... Oct 22, 2019 at 7:33

2 Answers 2

1

Restarting a server while something is rolling back, is almost always a bad idea. You may make things worse.

You don't say if you are using one of the repair options with DBCC CHECKDB if you are, it can complicate things even more.

It has been a few hours since the original question was posted, so things have probably either self corrected or gotten worse. Hopefully you have backups, that you will be able to use in the recovery, if things are not going well.

Some Related posts that may help

1
  • Great help thank you Oct 22, 2019 at 7:38
1

See Paul Randall's comments on DBCC CHECKDB. https://www.sqlskills.com/blogs/paul/the-curious-case-of-unstoppable-dbcc-checkdb/

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.