DBCC CHECKFILEGROUP bug fixed in 2008 SP1 CU6

Back in September I blogged about an old 2005 bug that prevented DBCC CHECKFILEGROUP checking the partitions of an object on the specified filegroup unless *all* partitions of the object are on the specified filegroup (not a smart way to set things up!). The bug was fixed ages ago in 2005 but has only just been fixed in 2008. The post which explains the bug in more detail is DBCC CHECKFILEGROUP bug on SQL Server 2008. This is an important feature to be able to split the consistency checks of a partitioned VLDB over a series of days – see CHECKDB From Every Angle: Consistency Checking Options for a VLDB for more details.

SQL Server 2008 SP1 Cumulative Update 6 (which you can get here) has the bug fix for 2008 finally. The KB article which describes the bug is 975991.

You’re all running regular consistency checks, right?

One thought on “DBCC CHECKFILEGROUP bug fixed in 2008 SP1 CU6

  1. I think the feature is fundamentally flawed in SQL2008 and SQL2008R2. I base this opinion on BOL and local testing. BOL for SQL 2012 reads the same so I assume the same behavior.

    One of the reasons I use multiple file groups in my 6 TB database is to ensure non-clustered indexes are on a different drive than the clustered index.
    Given this behavior and my approach, I am not able to do a partial restore for DBCC purposes. In fact I think the behavior is even more restrictive. I restored both theIndex file group and the corresponding data file group for a set of tables. CheckFG still disregarded the NC indexes in the Index File Group. And also according to BOL it will not check the NC index when it is run on the data file group. So, basically the NC indexes will never be checked unless I run CheckDB on the entire database. :(.

Leave a Reply

Your email address will not be published. Required fields are marked *

Other articles

Imagine feeling confident enough to handle whatever your database throws at you.

With training and consulting from SQLskills, you’ll be able to solve big problems, elevate your team’s capacity, and take control of your data career.