Timeline for Deciding on a replication strategy
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 10, 2014 at 8:35 | vote | accept | KenD | ||
| Nov 10, 2014 at 3:10 | comment | added | Kin Shah |
I have not seen any performance problems when the log backups are being restored on secondary (I am talking about more than 1000+ databases across 30+ instances around the world). For closing connections, there is an option when you configure logshipping to disconnect users when restoring the log files. So selecting that will take care of the users to disconnect.
|
|
| Nov 9, 2014 at 19:53 | comment | added | KenD | Thanks. "Standby" mode looks promising, but I've read something that suggest it can introduce some slowdown when restoring; given that I'll hopefully be restoring the log files into place every few minutes, and the secondary database will be used semi-regularly for reporting, should I expect any problems with performance or have to worry about connections being closed? | |
| Nov 9, 2014 at 19:34 | history | edited | Shanky | CC BY-SA 3.0 |
spelling
|
| Nov 9, 2014 at 16:54 | history | answered | Kin Shah | CC BY-SA 3.0 |