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

log shipping secondary database from standby to restoring mode Expand / Collapse
Author
Message
Posted Thursday, June 13, 2013 8:44 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, September 18, 2014 12:57 PM
Points: 394, Visits: 1,978
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?
Post #1463133
Posted Thursday, June 13, 2013 11:51 AM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 5:12 AM
Points: 5,863, Visits: 12,942
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.


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

Post #1463234
Posted Thursday, June 13, 2013 1:45 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, September 18, 2014 12:57 PM
Points: 394, Visits: 1,978
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

Post #1463288
Posted Thursday, June 13, 2013 1:50 PM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 5:12 AM
Points: 5,863, Visits: 12,942
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.


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

Post #1463292
Posted Friday, June 14, 2013 6:42 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, September 18, 2014 12:57 PM
Points: 394, Visits: 1,978
Thanks George. Is there any way we can introduce stripe backups in log shipping.
Post #1463531
Posted Friday, June 14, 2013 11:48 AM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 5:12 AM
Points: 5,863, Visits: 12,942
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


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

Post #1463718
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse