FIX: Couldn't truncate a partition of the partitioned table if it contains an extended or XML index in SQL Server 2016 or 2017

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


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. 


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


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


Learn about the terminology that Microsoft uses to describe software updates.