Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
sqldev80
Yak Posting Veteran
68 Posts |
 Posted - 2006-05-24 : 11:09:24
|
| how do i fix thisThe log file for database 'DATABASE_NAME' is full. Back up the transaction log for the database to free up some log space. |
|
|
datagod
Starting Member
37 Posts |
Posted - 2006-05-24 : 14:57:39
|
| backup log 'DATABASE_NAME' with truncate_onlyThen do a full database backup. Check your drive space as well. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-05-24 : 15:20:08
|
| Well it's only going to happen again. Your database recovery model is probably set to FULL and you aren't performing any transaction log backups. So to fix for good, check this out:http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=56434Tara Kizeraka tduggan |
|
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-05-24 : 21:07:49
|
i prefer to do a full backup before the truncate, then see if this free up space, if not then the truncate will be executed only if hard drive is unable to accomodate the growthin short: truncate is my last option for managing file growth --------------------keeping it simple... |
|
|
|
|
|
|
backup log file