- 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.
Article ID: 3188950 - Last Review: Sep 22, 2016 - Revision: 1