log shipping secondary database from standby to restoring mode

  • I am seeing high restore latency in log shipping. All the secondary databases are in standby recovery mode. We don't use these databases for any use. I would like to change them to restoring mode from standby read only mode to overcome this latency issue. I am sure this might not be totally contributing to the latency issue but expecting this might cut short the delay.

    What exactly happens while chaging this mode? What happens to the tuf file? In future if I want to get back to standby mode, can I do it?

  • its just a setting in the log shipping gui and affects the next restore. You can flip back and forth as you require.

    I can't see it having an affect on latency though I am not quire sure what you mean by latency in this case.

    ---------------------------------------------------------------------

  • I went through the below article which says about rollback processs happens in stand by mode which I am not sure. One other thing is in stand by it has to disconnect all the users before restore.

    http://askmesql.blogspot.se/2011/01/log-shipping-norecovery-vs-standby-mode.html

  • norecovery option would have to kick off connections as well.

    You would need a lot of uncommitted transactions I would say before getting a noticeable degradation in restore time.

    If by latency you mean there is a delay before the logs are restored that is a setting you can specify in log shipping for that - check it has not been set.

    ---------------------------------------------------------------------

  • Thanks George. Is there any way we can introduce stripe backups in log shipping.

  • I don't see an option to do that. Log backups would be read sequentially anyway so i do not think it would help.

    If you have the correct version of SQL and the latency is in the copy then backup compression would help

    ---------------------------------------------------------------------

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply