Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Shrinking the Transaction Log on a database that is involved in Log Shipping


Shrinking the Transaction Log on a database that is involved in Log Shipping

Author
Message
mcdba@russweb.co.uk
mcdba@russweb.co.uk
SSC Rookie
SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)

Group: General Forum Members
Points: 26 Visits: 224
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?



pradeep.mohan
pradeep.mohan
SSC-Enthusiastic
SSC-Enthusiastic (111 reputation)SSC-Enthusiastic (111 reputation)SSC-Enthusiastic (111 reputation)SSC-Enthusiastic (111 reputation)SSC-Enthusiastic (111 reputation)SSC-Enthusiastic (111 reputation)SSC-Enthusiastic (111 reputation)SSC-Enthusiastic (111 reputation)

Group: General Forum Members
Points: 111 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
Matthew Darwin
Matthew Darwin
SSC-Enthusiastic
SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)

Group: General Forum Members
Points: 197 Visits: 875
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 @EvoDBA

Check out my blog Natural Selection DBA
mcdba@russweb.co.uk
mcdba@russweb.co.uk
SSC Rookie
SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)

Group: General Forum Members
Points: 26 Visits: 224
It had grown as we had run out disk space on the target server.



Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search