I am trying to migrate the vCenter SQL DB to a dedicated SQL Server.
It already uses SQL Server but on the same VM as the vCenter installation.
Moving the DB and realigning the ODBC connection failed to start the vCenter service so I decided to re-install from scratch.
I pointed the vCenter installation to the ODBC link to the DB and expected to be promoted to use existing database.
This didn't' happen so I had to revert back.
Any reason why this didn't happen for me?
This link might be helpful
Do you have any screenshot from the error?
Please share more information about your environment.
No error it just doesn't ask me to use an existing vCenter DB once I select the ODBC link.
It carrys on as a normal blank installation...
Did you add your vCenter SQL user as db_owner of your SQL database and MSDB database?
Sure did. We are using sa credentials. I wonder if I should try Windows authenticatin?
Would you please share some screenshots from ODBC connection?
* It's recommended, use another user instead of "sa" for having more security and preventing damage to other database.
Not sure what versions of vCenter and SQL you are using. I had a similar issue a while back, the vCenter was looking for the same ODBC connection even though it was on a different server. Although the names did not match on the ODBC, vCenter was happy. Food for thought.
If the vcdb.properties file has entry of old SQL server, then virtual center server service will fail.
Please update the vcdb.properties file with new SQL server name and try starting vcenter service.
VMware KB: Moving the VMware vCenter Server 4.x/5.x SQL database