>Before moving to a recycling process did you Google [sql server delete no log] ?
>
>I haven't read any of the hits but what you're doing isn't unique so others may have found useful workarounds.
Thanks, this search is proven to be useful. I found some interesting topics.
This page discusses some of that:
http://www.sqlservercentral.com/Forums/Topic648742-338-1.aspxBut, there is one over there who votes for the importance of a rollback. Lets say I do not want a rollback because what I delete as to go no matter what.
Basically, what I was hoping for was a way to delete without any transaction log being involved. When I first tried that, I tried to do it in one command. That would be similar to what is being discussed at this page:
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/52e6be98-6165-4b1e-a926-5d5609ab8486/delete-large-number-of-rows-without-growing-the-transaction-log?forum=transactsqlBut, that was making the transaction log to crawl. So, I went into selecting all the primary keys I need to delete and delete one record at a time. While this is safer, it is not the faster way to do it.
They recommand a batch of 2000 records. But, this batch limit, in order to keep it safe, varies based on the environment. If I have to delete two million records every 30 minutes, deleting them 2000 at a time will still take a lot of time. I remember not so long ago we were able to achieve that in a fraction of a second. lol
...oh yes, there is TRUNCATE. But, that wipes out the entire table. I wish there would be something in the middle.
