In one of our ASP.NET Core applications, I added a new feature to cleanup old data. My implementation was simple and used a BackgroundService to run a cleanup script on periodic intervals:
All worked fine during development and testing, but when I deployed it to production it brought the whole application to a halt.
What was happening?
First, as this was the first time the script was run on production, there was a lot of old data. So while the query executed and completed quite fast on other environments, on production it impacted millions of rows.
What made the problem even worse is that the table that should be cleaned up contained a large amount of binary data. This made the transaction log grow in size and further increased the query duration.
My first attempt to improve the performance of this query was to delete the data based on the primary key. A suggestion I found here: How to Delete Large Amounts of Data – SQLServerCentral
However the impact of this change was minimal and the query still timed out.
I had not enough time to find a solution that allowed me to fix the issue at the application level. So I ‘hacked’ together a solution where I executed the query in small batches:
Using the query above the delete is executed in small batches of 100 rows with an interval of 1 second between every batch.
The total query execution time is still long but at least my application & database remained accessible during the execution.
Anyone with a suggestion for a better solution?