>As I saw from the Execution plat the most part of the operation if for recreating the clustered index.
>Could you try to remove the index first then DELETE and then recreate it?

Could it be that the index become bloated?

I recreated them all and the execution plan is showing something brand new, well scaled, with low numbers. So, it seems because that table is receiving new records every second, and that we do a regular maintenance on the Hit table that it was time to reindex everything. I always thought SQL Server was more robust in that direction. I will see, once we reindex on the production, if that helps.

The table I made the test on has 809796 records.