However, those items won??™t have been propagated to the secondary
server.
By far, the most common dependent item is a SQL Server login, whether it??™s via Windows
authentication or SQL authentication. As users are added to the primary database,
they will, of course, get restored on the secondary database. However, the logins associated
with those database users will not be moved. This will most likely result in a dreaded
orphaned user scenario in which the login and database users are out of sync. Rather
than spend another three to four pages explaining the entire orphaned user scenario and
how to work around it, I suggest simply firing up BOL and looking through the index or
doing a search for ???orphaned users.???
nNote If you??™re using Windows authentication for your SQL Server instances and they reside on the same
domain, the orphaned user scenario shouldn??™t affect you.
Step 5: Redirect Clients to the New Primary Server
BOL indicates that you simply need to redirect clients to the new primary instance. That??™s
easier said than done, and there isn??™t an automated technique for doing so.
Pages:
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324