You must manually intervene and tell the mirror database that it should
now assume the role of the primary database. Remember, there is no witness available to
facilitate failover.
Depending on the Service Pack level SQL Server is using, you probably won??™t be able
to access the graphical tools to perform the failover in the High Performance configuration.
From the command line, you??™ll actually have to break the mirroring session
completely:
ALTER DATABASE MirrorTest SET PARTNER OFF:
This command literally breaks the partnering session. Remember that this mirror
database has been sitting in an unrestored state the entire time, so you??™ll need to bring
it online:
RESTORE DATABASE MirrorTest WITH RECOVERY
Once the mirror database is online, there??™s no going back without re-creating a new
mirroring session.
Failback
It??™s in the failback process that you feel the sting of having no mirror. The only way you
can bring the database back online is to break the mirroring relationship completely. Of
course, that means you must rebuild the mirroring relationship. Thanks to the help of the
GUI, rebuilding database mirroring is relatively painless, as you??™ll learn in the upcoming
???Configuring Mirroring??? section.
Pages:
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396