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. Tuesday, October 20, PM. Regarding upgrading the IO Subsystem that was mentioned also:. I looked into them a while back for our system, but they were quite expensive. It seems like the prices have gone way down in the Solid State market recently.
And with the way Windows allows for better partitioning , it seems like an excellent choice for high load environments, like that described by Nik.
Or would you stay with the traditional drive structure? It also depends on what else is running and whether or not the DBCC finds any errors. If our DBCC runs for more than an hour, we can almost guarantee that it is going to return consistency errors.
In this case, it can sometimes run for 4 or 5 hours before returning those errors. You must be logged in to reply to this topic. Login to reply. Post reply. April 20, at am Please do not reply stating that it depends on the server hardware and it's specification. If you require any additional detail please let me know. Complicated Corruptions: Some corruptions need deeper reprocessing of data to figure out accurately where the corruption is.
Consistency check of GB database with only one table having three or four columns with documents or image files in filestream would process very quickly whereas another GB DB with tables and Millions of records could take a lot longer, even though the DB size remains same.
Consistency check of GB database with only one table having three or four columns with documents or image files inside varbinary columns would process a little bit faster compared to another database sized GB DB with tables and Millions of records as the earlier one has a single table whereas the latter has lots of tables and records.
Completed with inconsistencies identified — If any errors received, then it will be among the error descriptions. If not, please follow the next step. Please note that this may or may not have data losses, hence proper care should be taken while executing this option. Comments 0. Get Access.
Get access with a 7-day free trial. Try a week for free to see if you belong.
0コメント