FIX: DBCC CHECKFILEGROUP reports false inconsistency error 5283 on a database that contains a partitioned table in SQL Server

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core


Consider the following scenario:
  • You have a database that contains a partitioned table in Microsoft SQL Server. 
  • The table has a columnstore index, and the partitions of the table are mapped to different filegroups.
  • You run the DBCC CHECKFILEGROUP statement.
In this scenario, you receive the following false inconsistency error message:
Msg 5283, Level 16, State 1The Cross Rowset check on columnstore index object ID <object id>, index ID <index id>, partition ID <partition id>. Drop and recreate the columnstore index.

However, when you run the DBCC CHECKDB statement, you don't receive any consistency error messages. Additionally, running the DBCC CHECKDB statement together with the REPAIR_ALLOW_DATA_LOSS option doesn't fix the consistency errors. That's because the consistency error that's reported by DBCC CHECKFILEGROUP is a false positive and represents a reporting bug that can be ignored.


The issue is fixed in the following cumulative updates for SQL Server:


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.