VC 2.0.2 upgrade - SQL or VC first?

[dwchan]

We are about to upgrade our VC server from 2.0.2 to 2.0.1. In addition, our DBA want us to migration the current database for VC 2.0.1 from the SQL 2000 server to SQL 2005. My question is this. Should we leave VC alone for now, and upgrade our database from SQL 2000 to SQl 2005 first and make sure it is clean (assuming VC 2.0.1 suppose SQL 2000) than do the upgrade of VC. Or should we upgrade VC from 2.0.1 to 2.0.2 first, than go ahead and upgrade the database from SQl 2000 to SQL 20005?

dwc

[bertdb · Accepted solution]

double check the 2.0.1 install guide, but I'm pretty sure SQL 2005 was already supported (since around january 2007 iirc).

If that's correct, then it doesn't really matter, both upgrades are independent one of the other.

[Erik_Zandboer]

Bertdb is right I think, except when you are using SQL 2005 64bit edition. The 64bit edition is supported only in 2.0.2, so if you use 64 bit SQL 2005, it might be wise to upgrade VC first.

[dwchan]

but it is better to upgrade VC first before upgrade the database?

dwc

[surferdave]

I upgraded VC to 2.0.2 before upgrading to SQL 2005. I didn't have any problems.

[doctormiru]

See my upgrade path (changed to a new server with sql 2005)

1. Backup the existing DB

2. Create a new DB on SQL 2005 (dbVMVC)

3. Create ODBC Entry (VMware Virtual Center) Att! VC does not support SQL native client

4. Create SQL login (same user as old DB)

5. Restore DB from Backup

6. Fix sql permissions

EXEC sp_change_users_login 'Auto_Fix', 'sqlusername'

7. Remove must change PW Option:

ALTERLOGIN sqlusername WITH PASSWORD = 'NewPassword' UNLOCK MUST_CHANGE

ALTER LOGIN UserLogin WITH CHECK_EXPIRATION = OFF

ALTER LOGIN UserLogin WITH CHECK_POLICY = OFF

8. Installation of VC (be shure to preserve the database)

9. Run DB fixes

C:\Program Files\VMware\VMware VirtualCenter 2.0\

vpxd.exe -f DropVpxStatsRollupProc.sql -m

vpxd.exe -f rollup_mssql1.sql

vpxd.exe -f rollup_mssql2.sql

vpxd.exe -f rollup_entity_mssql1.sql

vpxd.exe -f rollup_entity_mssql2.sql

vpxd.exe -f updatedb_mssql.sql -m

13. Start VC Service

14. Ensure that the dir /tmp/vmware-root exists on all ESX hosts

15. Reconnect ESX Hosts

Regards

Michael

[jckowal]

DOCTORMIRU where did you get these upgrade steps from? Just wondering if they were published in some Vmware article or if you found them by experience.

[doctormiru]

Hi

The database fix steps are documented within the VC2.02 upgrade notes, The other points I could confirm after excessive testing and failing

regards

Michael