July 31, 2004 at 1:15 pm
how much time will it take to run dbcc checkdb in sqlserver 6.5 of database size of 10 gb
July 31, 2004 at 7:46 pm
The answer to this question depends on your hardware and configuration. I have a 40 GB database that takes 11 minutes to run DBCC CHECKDB on but this is SQL 2000 with a good number of disk drives.
The number of File groups, Data drives (logical and physical), the number of disk drives and raid configuration, and other processes running all impact the amount of time
August 1, 2004 at 3:16 am
Checked history for CHECKDB on one of our 6.5 boxes. DB is 25GB with about 9GB space free. Not sure if that means CHECKDB only had to check 16GB or the whole 25GB? Server is an Compaq DL580 with dual 2.8GHz Xeons, 2GB RAM, fast SCSI drives and Compaq RAID adapter, using RAID 5 for the DB & txlog. 1GB RAM is allocated to SQL, no other significant apps/services run on the box. Our last CHECKDB (run locally on the server, with no_infomsgs) took 4.75 hrs.
Checked history of same task on a dev 6.5 box. DB is 3.3GB, 2.2GB free. Box is older Compaq server, maybe model 3000, 7k SCSI disks, RAID 5, with single 300MHz Pentium 3, 255 MB Ram. 128MB RAM is allocated to SQL, no other significant apps/services run on the box. Just ran CHECKDB, took 6.75 mins.
PS - if you're running DBCC remotely (e.g.in query analyzer on your workstation) and don't use "with no_infomsgs" it seems to me that simply sending all that info back to the client has noticeable impact. More important for NEWALLOC, which spits out tons of output, than CHECKDB, but CHECKDB on my 3.3GB DB took a 7.75 mins when run w/out the no_infomsgs option, and there really was not very much output.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply