Do the deletion in chunks, but instead of trying to reduce the time between logs, back up the logs between chunks (that is, if you are in full recovery)
The problem is that the journal is full and therefore must grow. If it is full, an attempt to reduce it is useless; there is no free space in the log for accessing the OS. Instead, make the space inside the file reusable.
Since the database is in simple recovery, start the deletion in pieces with the CHECKPOINT command between each fragment. You cannot backup logs in easy recovery mode
, ( ). . , .
(SQL 2005 . SQL 2000 TOP SET ROWCOUNT)
DECLARE @Done BIT
SET @Done = 0
WHILE @Done = 0
BEGIN
DELETE TOP (20000)
FROM SomeTable WHERE SomeColumn = SomeValue
IF @@ROWCOUNT = 0
SET @Done = 1
CHECKPOINT
END
, - http://www.sqlservercentral.com/articles/64582/