Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Shrinking the Transaction Log on a database that is involved in Log Shipping Expand / Collapse
Author
Message
Posted Thursday, June 6, 2013 12:44 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, August 18, 2014 7:46 AM
Points: 18, Visits: 201
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?



Post #1460846
Posted Thursday, June 13, 2013 4:39 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Monday, July 28, 2014 12:44 AM
Points: 91, Visits: 322
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
Post #1462975
Posted Thursday, June 13, 2013 6:10 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, August 22, 2014 8:46 AM
Points: 146, Visits: 633
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.
Post #1463007
Posted Thursday, June 13, 2013 6:16 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, August 18, 2014 7:46 AM
Points: 18, Visits: 201
It had grown as we had run out disk space on the target server.


Post #1463015
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse