SQL Server 2005. transaction log file grows. Doesn't shrink even using backup in full recovery mode and backup of trn logs

SQL Server 2005

Have a maintenance plan that doesn't "shrink" the trn files.

The DB is approx 3 GB in size. The trn file is approx 12 GB in size.

Recovery mode is Full

Have just created another maintenance plan that takes full backup of the DB and backup of the transaction log. and do a shrink databases.

BUT the trn file is still 12 GB in size????????
Who is Participating?
momi_sabagConnect With a Mentor Commented:
is it possible that you have a transaction that has been running for a really long time and did not commit / rollback yet?
try checking it using sp_who2 according to the last_batchcolumn
maybe that is what causing the problem

did you try to stop and start the sql server instance?
TANGLADAuthor Commented:
I will try to restart the SQL service tonight.
Guy Hengel [angelIII / a3]Billing EngineerCommented:
run DBCC OPENTRAN to see if there is such a open transaction.

otherwise, your transaction log backup needs to be regulary, not only "once".
the shrink operation will then work, but not on the first run.
TANGLADAuthor Commented:
Solved. Ran the plan again and then the trn files was shrinked.

So the first time I run a trans-log backup it does not shrink the trn file, but the second time  it is shrinked.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.