In both access even though the mirroring was removed conventionally there appears to be a number of processes related to the mirroring that seem to persist.

Notably the BROKER_TASK continues to be seen as a significant wait type when on similar systems which never had mirroring it is not seen at all.

I have tried to help myself.On a test system I deleted broker related items and did remove the wait type and did not dame the server.However I was not comfortable or confident and was perplexed thinking that removing the mirroring should have put the system back to the sate it was in before mirroring was implemented.

I am left feeling that the only way back to the pre-mirroring sate is to reinstall - tell me I am wrong, please.

You may have to delete the mirroring endpoint as well if there are no databases mirrored. There are various other internal tasks to SQL Server that use Service Broker also. For details on Service Broker waits see the blog below.

Items 9 and 14 are missing from the screen shots. I assume you are referring back to the main 'Transaction Log Shipping' page in the properties view. It might be helpful to show the full screen shot. Thanks for the article.

Can you please explain why you disabled the restore transaction log job, and when it would be necessary to leave it on?

The reason for disabling the restore transaction log job on the secondary was given in the 3rd paragraph of the article.

"Once we convert the mirrored database to a log shipped database we can disable the restore job on the secondary and have the secondary available as a hot standby in case of an upgrade failure. This allows us to quickly backout of the upgrade by simply bringing the secondary online and pointing the application servers at it. Once the system is back online we can reestablish mirroring back to the original principal. If the upgrade is successful, we enable the restore job on the secondary, allow the secondary to catch up, and then reestablish mirroring."

If you are not planning to use the secondary as a backout plan for a failed implementation then you can just enable the restore transaction log job and convert mirroring to log shipping.

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.