OK so I've been tasked with upgrading an application which involves updating schema in a sql server 2005. Now I've been told their dr environment has a mirrored database. I've read the msdn article on mirroring but am unclear how it impacts my upgrade.
Do I: a) want to stop the mirroring (someone mentioned a wizard, but I'm not sure how I go about doing this) b) keep the mirroring in place because whatever I run on the primary database will flow through to the mirror
If I stop the mirroring do I then upgrade each database according to my scripts and then somehow set up the mirroring again? Or do I just apply my scripts to the primary database and do some kind of restore and set that up as a mirror.
As it is an existing mirror in a production environment I don't want to poke around too much in case I do something bad. Is there an easy way to grab their current settings so I can easily re-establish the mirror if I do have to stop it?
Thanks!
Edit - my other question is, with the transaction logs it looks like its being backed up every 15 minutes according to a schedule. Should I change the backup schedule whilst doing the deployment? I think one of my redgate schema changes scripts will take over 2 hours to run :) It is a big database!