Long running query with eager spool?
An eager index spool builds a temporary nonclustered index that is used for the duration of the query execution only – it is rebuilt each time. You may want to consider creating a permanent index on the base table instead. The properties of the spool indicate what the keys of the index should be:
The plan uploaded is anonymized, so you would need to inspect the real plan to determine the key columns and table name (for "Table5", which has 1,090,380 rows).