The top levels of the plan are concerned with removing rows from the base table (the clustered index), and maintaining four nonclustered indexes. Two of these indexes are maintained row-by-row at the same time the clustered index deletions are processed. These are the "+2 non-clustered indexes" highlighted in green below.
For the other two nonclustered indexes, the optimizer has decided it is best to save the keys of these indexes to a tempdb worktable (the Eager Spool), then play the spool twice, sorting by the index keys to promote a sequential access pattern.
The final sequence of operations is concerned with maintaining the primary and secondary
xml indexes, which were not included in your DDL script:
There is not much to be done about this. Nonclustered indexes and
xml indexes must be kept synchronized with the data in the base table. The cost of maintaining such indexes is part of the trade-off you make when creating extra indexes on a table.
That said, the
xml indexes are particularly problematic. It is very hard for the optimizer to accurately assess how many rows will qualify in this situation. In fact, it wildly over-estimates for the
xml index, resulting in almost 12GB of memory being granted for this query (though only 28MB is used at runtime):
You could consider performing the deletion in smaller batches, hoping to reduce the impact of the excessive memory grant.
You could also test the performance of a plan without the sorts using
OPTION (QUERYTRACEON 8795). This is an undocumented trace flag so you should only try it on a development or test system, never in production. If the resulting plan is much faster, you could capture the plan XML and use it to create a Plan Guide for the production query.