I am upgrading our Vmware environment from 5.0 to 5.5. It is all on virtual servers, so we decided to stand up new VM's for the new functionality then roll things over. I understand most everything about this process accept for how to handle the MSSQL database aspect. We were running 5.0 and MSSQL on the same VM in our 5.0 environment. I wanted to stand up a new VM to host SSO and Web Client service, another VM for vCenter and the Inventory service. Then I wanted to point that new set of resources at the instance of MSSQL running on our original VM from our 5.0 environment, turn off the old vCenter running there, install Update Manager, be done. Can I do it this way? I know I have to make a change in my existing vCenter server to put it into linked mode, and then bring up the other one in linked mode as I install it. Get them both up, float my ESXi Hosts over to the new one, shut down the old vCenter server instance, take new one out of linked mode. So I think I have a grip on the vCenter swap over, I just don't know about the MSSQL part. Can I stay with the same Database instance and have 2 vCenters pointing at it at the same time? Temporarily, if that makes a difference, it would only be that way until I floated the ESXi Hosts over, then the old vCenter server instance would go away. Or do I need to stand up another new VM with MSSQL and Update Manager on it and not reuse the old VM and it's MSSQL database? It's all virtual so I am good to do whatever, just need to know what would work best.
Thanks in advance for your time,