February 17, 2010 at 10:04 am
We are using SQL Server 2008 64-bit. The tables of one of our DW database ar loaded through SSIS packages. Recently, the load process is failed on Transaction_log full, and we noticed that the log has grown larger than the database. Any idea as how to control this growth? 😉
February 17, 2010 at 10:19 am
A trans log cannot actually get full. It can grow all the way to the capacity of the drive in which it resides.
You need to backup the database and truncate the log. Then you can shrink the file. The log is set to grow, usually automatically. Sounds like yours is running the drive out of space. Usually the database and log files are on two separate drives.
You can set the database to simple recovery mode, truncate the log and set the database back to full recovery.
Read the SQL BOL about log transaction logs
Andrew SQLDBA
February 17, 2010 at 12:57 pm
Please read through this - Managing Transaction Logs[/url]
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply