Can You Cancel DBCC Check DB Job

I have this job running for hours and it's causing a lot of I/O bottle neck on our server.
Other applications are timing out because of DBCC checkDB job.
Can I cancel this job?
FavorableAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Tony303Commented:
Yes you can, but it will take a long time to roll back what it is doing.
0
Tony303Commented:
Use the SSMS or run sp_who2 to derive the SPID that is running the DBCC.

Then you can issue a KILL command with STATUSONLY
to see the length of time to go...

Like this.
Transaction rollback in progress. Estimated rollback completion: 80% Estimated time left: 10 seconds.

KILL <yourSPID> WITH STATUSONLY;
GO
0
FavorableAuthor Commented:
We started the box bc there was no way to issue a kill statement.
We relocated our tempdb datafile to a newly allocated box two night ago; after we upgraded sql on the box to 2012.
 Could it contributed to this lots of I/O occurrences on C:drive.
It has never behave like this before.
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Tony303Commented:
What does the Status only statement show as estimated time?
KILL <yourSPID> WITH STATUSONLY;
GO

Is the TempDB log file still on C?
0
FavorableAuthor Commented:
We've contacted Microsoft.
0
Tony303Commented:
OK, let us know.
0
FavorableAuthor Commented:
Microsoft findings which they are going to fix tonight.
After the successful upgrade to SQL 2012, the system databases on SQL DATA ROOT remains on 2008 version, current version on the system registry is still pointing to 2008 and the start up parameter also on 2008, yet we had a successful upgrade. Very bizarre situation.  These are the things we are going to be fixing tonight.  
They advised that even though we are on 2012 SP1, there's CU fixes 6 released for 2012 SP1 that we also have to apply.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Tony303Commented:
Good speedy response from MS.
Good luck, go well.
0
FavorableAuthor Commented:
thanks everybody for your responses
0
FavorableAuthor Commented:
why is close request pending?
0
FavorableAuthor Commented:
Microsoft help to resolve the issue.
The resolution was that we contact our disk vendor to analyze our disk for speed. For SQL Server update with full scan.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.