Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Symptoms

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.

Resolution

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

Cumulative Update 2 for SQL Server 2016

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:

Latest cumulative update for SQL Server 2016

Status

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

References

Learn about the terminology Microsoft uses to describe software updates.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×