If you??™re frequently backing up transaction logs
at the primary server (which you??™re probably doing to minimize the possible data
CHAPTER 6 n MAINTAINING A WARM STANDBY SERVER VIA LOG SHIPPING 162
latency between the primary and secondary servers) and you check the ???Disconnect
users??? option, users of the secondary database will have a frustrating experience when
running reports. Plan carefully before choosing the ???Standby mode??? option. It can be
useful, but you should probably change the frequency of your restore operations to
coincide with the downtime of the secondary database.
Figure 6-15. When you check the ???Disconnect users??? option, users are forcibly kicked
from the secondary database when a transaction log restore occurs. Standby isn??™t nice
enough to wait for executives to finish running a report.
The benefit of automated log shipping is that you can repeat it for additional
servers. For instance, if you happen to have a server a few cities away and can afford to
back up, copy, and restore transaction logs on a more frequent basis, you can add that
distance server as another secondary node.
Pages:
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318