A historical SQL Server 2017 Bug affected CHECKDB with PHYSICAL_ONLY and clustered columnstore data. One client observed a dump.

The behavior differed from the client SQL Server 2016 environment. My investigation linked Microsoft KB4462767. Match that symptom to its exact build context. Later columnstore fixes can address different symptoms.
-- Historical failing-check shape for the reported SQL Server 2017 build:
-- DBCC CHECKDB WITH ALL_ERRORMSGS, NO_INFOMSGS, PHYSICAL_ONLY;Record the full error, dump details, build and database features. Compare the documented fix and current servicing history. Test the supported update on a copy. Don’t remove production columnstore indexes merely to experiment.
PHYSICAL_ONLY is a reduced check. Full CHECKDB includes broader logical checks. Different outcomes need investigation. Removing columnstore indexes is not an established workaround for this symptom.
Reference: Original Microsoft columnstore CHECKDB fix.
Related reading
A passing integrity check is not an explanation for a failing check, it is another result to investigate.
Published by Pinal Dave on SQLAuthority. More of my work at pinaldave.com.
Discover more from SQL Authority with Pinal Dave
Subscribe to get the latest posts sent to your email.




