Why delete older events in blocks of 5000?
As long as the DB server can handle it (transactional log sizes/disk space etc..) why not increase it to 50,000 or 500,000?
I suppose ignorance is the main reason why. I'm by no means a SQL expert. For the system that filled up a partition previously, I shrank the transaction log prior to deletions and had it down to under a Gig. After starting the event deletions though, it has grown back up to 12 Gig. I'll try to increment it up per your suggestion and see how that works. Thanks for your suggestion Tristan! My newness to this is really showing so I did want some other eyes on the situation to give me a 'sanity check' of what I'm doing to clean up the databases.
This is an update.
I have shrunk the databases and added all the 'purge' tasks I could find to keep this from happening again. The number of events has dropped but the larger site (after four days) has only dropped from a previous high of over 180 million events (Event ID 18002) to 95 million. This is a slow process. I'm still curious as to the number of 18002 events though. Has anyone else experienced this?