Tag Info

New answers tagged


Your only solution for this problem is to take a backup of the datafiles that are hit by a direct load operation, or prevent force_logging operations totally. Force_logging operations may seem like a good idea, performance wise but if you care about your data ..... don't do it. alter database noforce logging;


Use a loop to delete and make frequent transaction log backups while doing so. That way people can use the table and you will keep the transaction log at a responsible size DECLARE @ROWCOUNT int = 1 WHILE @ROWCOUNT > 0 BEGIN delete top (10000) from [SomeTable] where [Something] set @rowcount = @@rowcount; END;

Top 50 recent answers are included