http://blogs.msdn.com/sqlserverstorageengine/archive/2007/01/24/how-long-will-checkdb-take-to-run.aspxThis is a question I see every so often and it cropped up again this morning so I'll use it as the subject for this week's blog post. There are several ways I could answer this: the unhelpful answer - I've got no idea. the almost-helpful answer - howenCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/sqlserverstorageengine/archive/2007/01/24/how-long-will-checkdb-take-to-run.aspx#1559104Wed, 31 Jan 2007 00:26:22 GMT91d46819-8472-40ad-a661-2c78acb4018c:1559104Peter Wijntjes<p>Although you explicitly state not to delete logfiles from SQLServer 2005 database I have run into a situation where I do not see this to be a problem. </p> <p>I would like to see what my mistake is in the following scenario.</p> <p>Data and Logfiles are replicated continuously. (by the storage area network, a duplication of every disk is replicated to a safe external location).</p> <p>A user database backup is made every night. </p> <p>During the day the transaction log is not backed up. The policy is as follows: If disaster strikes we can always use the replicated disks to go back to a checkpoint somewhere during the current day without any restore operation.</p> <p>If disaster realy strikes we can use the backup which will always bring us back to the situation where we where when the backup was created. There are no 2 phased commit situations (like your bank example).</p> <p>In short, what is possible the problem if I have created a data-backup at a moment when no one is using the database but no backup of the log file?</p> http://blogs.msdn.com/sqlserverstorageengine/archive/2007/01/24/how-long-will-checkdb-take-to-run.aspx#1566656Wed, 31 Jan 2007 21:25:59 GMT91d46819-8472-40ad-a661-2c78acb4018c:1566656Paul Randal - MSFT<p>I'm not clear on what you're asking. If you take a full backup, that also includes any log necessary to create a transactionally consistent view of the database. Can you rephrase the question please?</p> http://blogs.msdn.com/sqlserverstorageengine/archive/2007/01/24/how-long-will-checkdb-take-to-run.aspx#2571335Sat, 12 May 2007 16:32:49 GMT91d46819-8472-40ad-a661-2c78acb4018c:2571335Brian H. Madsen - .Net Powered by Caffeine<p>The Perth SQL Server User Group was lucky enough to have Paul Randal , Principal Lead Program Manager</p> http://blogs.msdn.com/sqlserverstorageengine/archive/2007/01/24/how-long-will-checkdb-take-to-run.aspx#4416745Thu, 16 Aug 2007 18:17:16 GMT91d46819-8472-40ad-a661-2c78acb4018c:4416745zsrogers<p>My experience with DBCC CHECKDB is usually this.</p> <p>If the procedure has never been run or it has been a long time since last time it was run it will take a lot longer that if it was recently executed.</p> <p>The problems it is trying to correct are cumulative and have a direct influence on how much work needs to be done.</p> http://blogs.msdn.com/sqlserverstorageengine/archive/2007/01/24/how-long-will-checkdb-take-to-run.aspx#9615856Thu, 14 May 2009 15:56:14 GMT91d46819-8472-40ad-a661-2c78acb4018c:9615856Blogs from Suhas<p>In this post, we would have a look at the differences between DBCC CHECKTABLE and DBCC CHECKDB. We would</p>