June 6, 2013 at 12:44 pm
Hi,
One of the Sharepoint databases that I Logship to our DR site has got a Transaction Log file that is much bigger than it needs to be. So I would like to reclaim some of the space tied up it. What I am not sure about is whther or not I can just shrink ot in the normal way i.e. DBCC SHRINKFILE, or do I need to do something different so as to not mess up log shipping?
June 13, 2013 at 4:39 am
Yes, its really affect the log shipping configuration.
You can remove the log shipping and change the recovery model from Full to Simple and then shrink the log files and again configure the log shipping.
Pradeep
June 13, 2013 at 6:10 am
This isn't true, you can shrink a transaction log file that is in a log shipping configuration without affecting the log shipping.
However, I'd only do it if the log has grown on a one off disproportionate amount (e.g. an excessively large transaction, or if for any reason your log backup job failed for any period causing unnecessary log growth), otherwise the log will simply grow back to that size.
If that's the case, then you're better off performing your log backups more frequently.
Follow me on twitter @EvoDBACheck out my blog Natural Selection DBA[/url]
June 13, 2013 at 6:16 am
It had grown as we had run out disk space on the target server.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply