Dan Guzman - Not the MVP (8/19/2010)
So, this example is only intended for fail implementations? You plan on reverting back to mirroring when the implementation is complete?Or, did you mean to include a statement to come back later and turn on that job after the code implementation was complete?
Once the code upgrade completes successfully the LS restore job can be turned on to catch up the secondary. Then we can reestablish mirroring for high availability.
The reason for switching to log shipping from mirroring is to have that "hot" standby copy ready on the mirror/secondary server which the application servers can point to. This brings the entire system back online faster in the event of a code upgrade failure. The traditional way of backing out of a code upgrade would be to restore the principal/primary database from backup. That may take several hours depending on the size of the VLDB creating a longer backout time.