|
sql
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Log Error
Hi I am getting the follow error
'log file for database dbname is full, please backup the transaction log for the database to free up some space.' running backup log dbname with truncate_only sorts it out. All's I want from my back up is to take a copy of some small databases every night. What I am doing wrong to cause the log files to continue growing. I'm a designer not an administrator so it is a little out of my area! Hi Chris
You may have a fixed size allocated to the database and in some circumstances this may not be sufficient. The may help you understand the log file architecture: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_da2_876t.asp?frame=true and the whole chapter is a good read! http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_da_7v1h.asp?frame=true This may also helps: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_da2_1uzr.asp John Show quoteHide quote "Chris Kennedy" <chrisknospam@cybase.co.uk> wrote in message news:O9744SeXFHA.2128@TK2MSFTNGP14.phx.gbl... > Hi I am getting the follow error > > 'log file for database dbname is full, please backup the transaction log > for the database to free up some space.' > > running backup log dbname with truncate_only sorts it out. All's I want > from my back up is to take a copy of some small databases every night. > What I am doing wrong to cause the log files to continue growing. I'm a > designer not an administrator so it is a little out of my area! > To add to John's response, you can set your database recovery model to
SIMPLE so that committed data are automatically removed from the log. The SIMPLE recovery model is appropriate when your recovery plan is to restore from your last full backup and it is acceptable to lose data modifications made since the backup. -- Show quoteHide quoteHope this helps. Dan Guzman SQL Server MVP "Chris Kennedy" <chrisknospam@cybase.co.uk> wrote in message news:O9744SeXFHA.2128@TK2MSFTNGP14.phx.gbl... > Hi I am getting the follow error > > 'log file for database dbname is full, please backup the transaction log > for the database to free up some space.' > > running backup log dbname with truncate_only sorts it out. All's I want > from my back up is to take a copy of some small databases every night. > What I am doing wrong to cause the log files to continue growing. I'm a > designer not an administrator so it is a little out of my area! >
Other interesting topics
Shrinking the Transaction Log
Access 97 to SQL Fiscal or Calendar Year Function error CASE Statement reliable way to identify all dependencies? Transaction log backup in suspect mode DB Consistency Errors occurring frequently on random tables database marked as "Suspect" altering a primary key property How to store euro currency symbol? |
|||||||||||||||||||||||