Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Can somebody please, let me know that how can we find out that the transaction log is full OR How can we figure out that what is causing the transaction log to grow.. Please, help.


share|improve this question

migrated from Sep 19 '09 at 2:55

This question came from our site for professional and enthusiast programmers.

you have asked 18 questions and accepted none of them. – Mitch Wheat Sep 19 '09 at 2:53

The transaction log in a user database will grow because the database is set to full recovery, and the transaction log is not being backed up. If you don't need the ability to do point in time restores then you should change the database recovery from full to simple.

If you do need point in time restores then you need to start backing up the transaction log.

share|improve this answer

Have a read through this, see if it helps - Managing Transaction logs

If the log is filling up, generally either the max size is too small or you're running in full/bulk-logged recovery model and you're not backing the log up.

share|improve this answer

This probably belongs on

Short answer is, however, lots of reads/writes is causing this. Increase the size of the log or run DB maintenance and backups more frequently.

share|improve this answer
Specifically log backups – GilaMonster Sep 19 '09 at 10:34

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.