Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. 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

We have a transaction log on a sql database and for some reason it has filled up to 50GB when our live system only has about 2GB. Is there any way I can profile sql or the transaction log to try and find out why this particular one has grown so much?

share|improve this question

migrated from Oct 10 '12 at 12:47

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

What recovery model are you using? Full..simple? Do you create Transaction Log Backups or only Full Backups? If you don't know the answer to these, I suppose it's yes to both, so you should first follow Remus's advice. – Marian Oct 10 '12 at 23:04

Start by investigating what is holding up the log reuse. Read Factors That Can Delay Log Truncation, look at log_reuse_wait_desc value is sys.databases. Based on what you find there, there could be several potential actions.

share|improve this answer

I would guess that you are not backing up the transaction log. This is not the same thing as backing up the database. I would suggest you back it up at least daily. In a high transaction environment, it should be backed up more frequently, ours is backed up every 15 minutes.

share|improve this answer

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.