Failback is another story. Yes, it should be seamless to users when it happens, and
quite easy once the principal is restored. That is, if you remember not to back up the
transaction log, truncate it, or switch to Simple Recovery mode while the mirroring configuration
is in a failover state. Remembering to leave the transaction log alone during
a failover state is all you need to do during a failover situation. Once you restore the
principal, you can usually just fail back immediately to the principal. Sometimes the
principal may be so badly damaged that you have to eliminate and reconfigure mirroring
from scratch, but High Availability mode is designed to minimize those situations.
CHAPTER 8 n DATABASE MIRRORING 210
ORPHANED USERS: AN OLD FRIEND
Anyone who has backed up and restored a database to a new server has probably run into the problem
of orphaned users. Regardless of what mode you??™re in, you??™ll experience the same issue in all database
mirror failover situations. If you haven??™t dealt with the issue of orphaned users, here??™s a quick recap.
SQL Server has both logins and users.
Pages:
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404