Symptoms
Assume that you create or rebuild a filtered index in Microsoft SQL Server 2014, 2016 or 2017. When you try to create or rebuild the filtered index, if the optimizer picks a parallel index intersection (join) plan, then the resulting index may be corrupted. Subsequent queries may produce wrong results and subsequent inserts, updates and deletes may encounter errors.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Resolution
This issue is fixed in the following cumulative updates for SQL Serve
- Cumulative Update 16 for SQL Server 2017
- Cumulative Update 7 for SQL Server 2016 SP2
- Cumulative Update 15 for SQL Server 2016 SP1
- Cumulative Update 4 for SQL Server 2014 SP3
- Cumulative Update 16 for SQL Server 2014 SP2
About cumulative updates for SQL Server:
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 on SQL Server 2017
- Latest cumulative update for SQL Server 2016
- Latest cumulative update for SQL Server 2014
References
Learn about the terminology that Microsoft uses to describe software updates.