A small misunderstanding about SQL Server mirroring

Yesterday evening suddenly received a customer's call, said in the configuration of the mirrored production environment database to modify the "committed read snapshot" option when the error, you need to cancel the image and then re-build. The sad thing is that it's a near-TB database and ask me if there's any quick way. So I asked the client why he thought it was a long time, and he said it would take a lot of time to do a full backup and then restore this step to the mirror node when the image was re-built. So does this really need to be done?

Modify the Read Committed snapshot option under the mirrored database

After you cancel mirroring, you will see the status of the database of the mirror node from "mirrored, synchronized/restoring" to "restoring ..." and not deleting it, it is also useful.

Modify the option to reconfigure the image after successful, the point is that the mirror node does not need to restore the full backup, directly through the management tool configuration.

The misconception is that when you cancel mirroring and rebuild it, you do not need to do a full backup on the principal node database and restore it on the mirrored node. There is a small detail here is if you do a log backup on the database of the principal node after the image is canceled, it's a bit of a hassle, and it's not going to start here.

　　

A small misunderstanding about SQL Server mirroring