Transaction Log keeps growing even continue to run Backup Log with Truncate_only on DB
Posted on 2014-12-23
On my MS SQL 2005 test db server, I made a change to use a store procedure to update about 35K records in the database. The transaction log kept growing when the procedure was run until I ran out of disk space (Log file grew more than 250GB). I set the database recovery mode to Simple and scheduled backup of log using "with Truncate_only" to happen every five minutes, but that didn't stop the log from growing. Any suggestion on how to stop the log from growing? I can't modify the store procedure which came in on a commercial product that is locked. I like to use this procedure to update the db, so I won't risk introducing any database integrity issues into the db.
Thank you very much in advance for your help.