DBCC CHECKDB is taking to long

Question

DBCC CHECKDB is taking to long

MTY-1082557

SSCarpal Tunnel

Points: 4540
More actions
December 7, 2009 at 2:00 pm

#140444

I have a database in Simple Model Recovery. We only use this DB to load data from flat files. The full backup runs every Saturday and the differential runs every night (except Saturday).
This weekend it performed the full backup with no problem at all. Sunday and Monday got an error in that specific database. The Job Process stayed in KILLED/ROLLBACK Status. I Killed the process and it took like 1 hour. My IT guy detected some use memory running. Probably this process, we are not sure.
Since then, the DB takes awhile to run a simple select statement, even if its only one row set of result.
I’m running a DBCC CHECKDB to verify that my database is not corrupted or any page damage. The DBCC has been running for 3 hours now. Not process are blocked, nothing else is running except this DBCC, I can do select in the database, but not inserts.
The database has partition in 2 main tables and contains 25 files/filegroups.
Is normal for the DBCC to take that long? This is my database sizes;
database_namedatabase_sizeunallocated space
Database723242.56 MB667442.68 MB
reserved data index_sizeunused
48320328 KB24344824 KB23971160 KB4344 KB
Any advice?

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

GSquared SSC Guru Points: 260824 More actions · Answer 1

How long will depend on the hardware, but a 700 Gig database will take a while to check. Hours doesn't sound outrageous to me.

- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread

"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

HBK_4700 SSCrazy Eights Points: 8932 More actions · Answer 2

If DBCC CHECKDB is taking longer than usual, there must be something wrong.

Please wait for CHECKDB to complete.

Meanwhile check below link.

http://www.microsoft.com/emea/teched2008/itpro/tv/default.aspx?vid=78

MTY-1082557 SSCarpal Tunnel Points: 4540 More actions · Answer 3

MTY-1082557

SSCarpal Tunnel

Points: 4540

December 7, 2009 at 2:38 pm

#1088909

should I stop it?

It has 3:23hours already

SQLRNNR SSC Guru Points: 281334 More actions · Answer 4

I would let it run to completion if at all possible.

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 5

MTY-1082557 (12/7/2009)
should I stop it?
It has 3:23hours already

No. Let it run to completion. Stopping it won't cause any problems, but you also won't get any results, essentially wasting the hours that it's been running

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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

HBK_4700 SSCrazy Eights Points: 8932 More actions · Answer 6

@MTY-1082557

Any update, did you resolve the issue. Please post output of CHECKDB

MTY-1082557 SSCarpal Tunnel Points: 4540 More actions · Answer 7

Hi all,

I didnt have any chance to post the results 'cause we are with another issue.

The CHECKDB never end. It was still a KILL/ROLLBACK process "running". So when we killed the process the CHECKDB stopped.

We reboot out server and re run the CHECKDB again and only took 5 minutes with no error at all.

Seems like the KIL/ROLLBACK process was blocking everything else.