August 13, 2012 at 4:29 pm
Hello -
I have a situation where I am being asked to implement mirroring for a SQL Server 2005 Standard Edition instance that is comprised of about 15 databases, all totaling about 500gb in disk space. The target, 2-B mirror server is currently running the Enterprise Edition of SQL 2005, and obviously that is not going to work. So - I am having to put Standard Edition back in place to make this happen. Reason for this is due to my company not wanting to take an outage to migrate this instance from Standard Edition to the new Enterprise Edition instance.
My question is this - will it even work? They are thinking that once it is fully in sync, that we can break the mirror and things will be ready to roll, but I know that is not the case (IP address and Server name alone with the way the applications have been designed is not going to allow that to work properly).
I don't see a solid way for this to happen without an outage taking place, so it is just drawing me back to the very straight forward, and simple means of a planned/announced outage, straight file copy of the .mdf/.ldf, then mount, test, deploy type scenario.
Thoughts? Suggestions?
Thanks in advance...
August 15, 2012 at 4:22 pm
Since I first posted this question, I have done other research and scouring - I cannot find a single documented instance where mirroring was used as a migration tool. If I do not hear anything else out here on it, I will assume what I already thought - that of it being a really bad idea!
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply