question

David Wimbush avatar image
David Wimbush asked

Log shipping transaction log sizes

I'm log shipping a couple of dozen databases from 3 live servers onto a single standby server. The transaction log files disk on the standby server is getting pretty full so I need to do something. There's a lot of unused space in some of these log files (which are matching sizes on live and standby). Some of them are only that big because of major refactoring excercises, and don't need to be that big normally, so I reckon I can shrink them on the live server. But will that action get shipped over and repeated on the standby? Somehow I doubt it.

The standby databases are in Standby / Read-Only mode. Can you suggest a way I can shrink the logs on both live and standby without breaking the log shipping cycle, please?

sql-server-2005log-shipping
10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

·
David Wimbush avatar image
David Wimbush answered

Case solved. I shrank the log on the primary database like this:

use [TfsVersionControl]
go
dbcc shrinkfile (N'TfsVersionControl_log' , 100)
go

and that activity WAS log shipped over to the secondary, and the log shrank there too.

Wicked!

10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.