Error: Transaction log is full.

Question

0.00/5 (No votes)

See more:

The transaction log for database 'britco_dbase' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases.

This error comes when i take the website,So i chat with the rds server and they clear the log file.At that time it will be solved.But after some days, when we insert new data,then also the same error comes.So how to solve this problem permanently?

Posted 1-Sep-11 19:18pm

RoshInd

Updated 1-Sep-11 22:30pm

Prerak Patel

v3

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dylan Morley · Accepted Answer · 2011-09-01T22:41:00

Perform regular backups of your database \ TLogs

http://msdn.microsoft.com/en-us/library/ms175495.aspx[^]

http://msdn.microsoft.com/en-us/library/ms179478.aspx[^]

Depending on how many transactions your application is processing (and how much disk space you have etc!) you should be performing regular backups.

If you don't want this level of disaster recovery, you could consider changing your database model to 'Simple'. This means you'd only be able to restore your database to 'last known full backup', rather than point-in-time recovery that regular TLog backups offer. In this case, you should have an automated job that's creating a full db backup (maintenance plan etc)