TANGLAD
asked on
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????????
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????????
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
![Avatar of Guy Hengel [angelIII / a3]](https://filedb.experts-exchange.com/files/public/2013/11/25/ddbe0ea6-aa6e-4279-b781-57b735dd3ea0.jpeg){kind=small}
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.
otherwise, your transaction log backup needs to be regulary, not only "once".
the shrink operation will then work, but not on the first run.
ASKER
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.
So the first time I run a trans-log backup it does not shrink the trn file, but the second time it is shrinked.
ASKER