July 27, 2007 at 5:15 am
Hi ,
I have a database of approx. size of 35 GB. The size of the log file became 3 GB few days back. I used dump tran statement and then ran Shrink database . Still the size of the log file is 3 GB.
Why this must be happening? Is there any way I can reduce the log file size?
- The data base is set for transactional replication wih another server in other country. Is that causing this problem?
Thanks in Advance.
Regards,
Rohit
July 27, 2007 at 6:17 am
I am not sure if the Replication is causing the issue. You should have good backup plan. That will solve the issue.
Please follow these links for more info:
http://support.microsoft.com/kb/272318/en-us
http://support.microsoft.com/kb/814574/en-us
http://support.microsoft.com/kb/873235/en-us
Minaz
"More Green More Oxygen !! Plant a tree today"
July 27, 2007 at 10:22 am
A few things. First, what caused the log to grow? This stores a record of the work done in the db, and if there's a lot of work (inserts, updates, deletes) you might need to have a log file that size. It doesn't necessarily help to shrink it and have it grow.
The other thing is that you might need a full backup and be sure there are no open transactions. There are virtual log files in the physical file and if the active one is near the end of your file, you cannot shrink it. This script might help: http://www.sqlservercentral.com/scripts/viewscript.asp?scriptid=26
Also, be sure you shrink just this file and not the db.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply