I have a table that has gotten a little out of control. I am not a DBA per se but seem to recall that deleting a huge volume of rows in one shot can cause transaction log issues, hamper overall system performance during the delete, etc...
Is there an efficient way for me to create a job that deletes records in small batches to over hampering other access/performance and prevents problems with the transaction log?
This process can be quite slow is that makes a difference
For additional context, the delete criteria will be based on something like... where x like '%blah%'
. Also, there is one clustered index and 5 non-clustered indexes.