How long dbcc checkdb

Improve this question. Marcello Miorelli Marcello Miorelli Add a comment. Active Oldest Votes. Improve this answer. AdamRidgway AdamRidgway 21 4 4 bronze badges. This does not work for me. I ran DBCC check 3 hours ago, and this returns nothing. I think it only works if there is an error..

I figured out what happened. I ran DBCC checkdb a second time and this code works great. Have you checked the file level wait statistics for tempdb and your user database? The below script might be able to help. Thanks shankar.. A significant jump in execution time is usually a sign that you have a corruption issue, so if you are killing CHECKDB, then you aren't helping yourself.

As Sankar points out, you have a problem with your IO Subsystem being a bottleneck, but I wouldn't attribute that to causing the CHECKDB to run 4 times longer than normal without first knowing that it completes successfully without reporting errors. Also, having a significant slow down in disk performance would be a sign to me of either imminent failure of a hardware component, or that a component already failed.

If you have RAID 5 and you see a significant degredation in performance it could be that you have lost one of your disks and you are running on borrowed time. If you have a failed disk in your RAID 5 array, one more failure and you have lost your array.

Updated: Edited by: Andrew Leniart Mark Wills. Includes estimated times to repair database corruption's in production databases. If the used space size in the particular database is huge, then it has to read a lot of pages which means a lot of IO. CHECKDB takes great pains to do the most competent IO and read the database pages in their physical order with sufficient readahead so that the disk heads move smoothly across the disks rather than jumping around randomly and experiencing disk head seek delays.

Density of the Database Schema: The more objects present in the database, the more structures that need to be consistency checked. Complicated Corruptions: Some corruptions need deeper reprocessing of data to figure out accurately where the corruption is. Your only hit would be the full crawl which you would probably want to run in off-peak hours Sign up to join this community.

The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Asked 12 years, 4 months ago. Active 12 years, 4 months ago.

Viewed 11k times. Is that normal? How long should it take? Improve this question. Sruly Sruly 1 1 gold badge 4 4 silver badges 6 6 bronze badges. Add a comment. Active Oldest Votes. Here you go: There's only one time when you should be trying to work out how long a CHECKDB is going to take - when you're planning your regular database maintenance.

There are several ways I could answer this: The unhelpful answer - I've got no idea. The almost-helpful answer - how long did it take to run last time and are the conditions exactly the same? The answer I usually give - it depends. The size of the database Pretty obvious