Updating while compression is in progress can lead to nonclustered columnstore index corruption in SQL Server 2016

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


Consider the following scenario:
  • You create a nonclustered columnstore index in an instance of Microsoft SQL Server 2016.
  • You run an ALTER INDEX REORGANIZE statement, or the Tuple Mover task that compresses columnstore data runs in the background.
  • At the same time, you execute a DELETE or UPDATE statement that modifies the nonclustered columnstore index.

In this scenario, index corruption can occur. The rows that were deleted or modified appear in the nonclustered columnstore index but not on other indexes for the table.


The fix for this issue is included in the following cumulative update for SQL Server:


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


Learn about the terminology Microsoft uses to describe software updates.