SQL Server Performance

Log shipping and shrink

Discussion in 'SQL Server Log Shipping' started by Aidan, Jul 3, 2006.

  1. Aidan New Member


    I have a primary/secondary log shipping pair and the the size of the database is getting too large. Because of other constraints I cannot shrink the live database.
    I intend to archive data off the standby, and then shrink the standby and then make this the primary, creating a new standby as part of starting the log shipping process.

    Can anyone see any issues with this? Will I have to stop applying logfiles to the secondary while I shrink? Can I then resume log shipping? Or does shrinking wreck the log shipping process?

    Thanks everyone!
  2. simondm New Member

    You can't make any changes to the standby server as the db is read only. You'll need to shrink the live server if you really need to do this.

    Sorry thats probably not much help!
  3. Aidan New Member

    Yes, you are right Simon.

    I decided to set it up and try it out and of course you are correct. I had thought - silly me - that restoring the master database etc over the top of the secondary would fool it, but of course it doesn't.

    Back to the drawing board!!!!!!!!

Share This Page