I was previously asked by a customer "What is the best way to move a VMM SQL database to another server?". The customer also advised that they had attempted to research the scenario, but were not able to find any documentation/blogs. So without "official" guidance I worked with the customer to create a Migration Task List. Following the items on the list we successfully moved their VMM DB between the SQL servers, "Hooray!!" . Unfortunately I am unable to personally assist everyone that has to do this, which is why I have put this article together, to highlight the steps we performed and hopefully help anyone else faced with a similar task:
The final task list included 22 steps, split into 3 sections (Prerequisites, Implementation and Testing). The majority of the steps involved were environmentally specific and will not apply to all setups. So here are the generic tasks that we had to complete in order to achieve a successful DB move:
Implementation(If you have a standalone VMM Management server perform Steps 4 and 6)
(Each VMM environment/IT Admin may have their own testing plan to confirm functionality)
The above steps will also apply, in most cases, when upgrading your VMM installation. However, you will need to perform additional tasks (example: upgrading the Vmmagent version on the hosts) to complete a successful upgrade.
I have not been able to find any documentation about upgrading the build of a VMM SQL Server. I am a DBA so I have no real ideas about SCVMM management. Thanks Chris