Operational Defect Database
BugZero found this defect 1308 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Microsoft SQL Server | 10870647
KB4024622 - FIX: Couldn't truncate a partition of the partitioned table if it contains an extended or XML index in SQL Server 2016 or 2017 - Microsoft Support
Last update date:
7/21/2023
Affected products:
SQL Server 2016 Developer - duplicate (do not use)
SQL Server 2016 Enterprise - duplicate (do not use)
SQL Server 2016 Enterprise Core - duplicate (do not use)
SQL Server 2016 Standard - duplicate (do not use)
SQL Server 2016 Service Pack 1
SQL Server 2017 on Windows (all editions)
Affected releases:
build lower than 14.0.3006.16
Fixed releases:
14.0.3006.16
Description:
Symptoms
Assume that you create an XML index or extended_indexes (such as a spatial index) on a partitioned table in Microsoft SQL Server 2016 or 2017. When you try to truncate a partition of the partitioned table with the TRUNCATE TABLE WITH PARTITIONS command, for example, "Truncate Table PartitionedTable by using (PARTITIONS(PartitionNumber))", the operation may fail.
Resolution
This issue is fixed in the following cumulative updates for SQL Server: Cumulative Update 1 for SQL Server 2017 Cumulative Update 4 for SQL Server 2016 SP1
