2,187
edits
m (Minor typo correction) |
(Added "Migrate SQL2000 to SQL2005") |
||
Line 50: | Line 50: | ||
== SQL Database == | |||
=== Migrate SQL2000 to SQL2005 === | |||
This should be fairly painless (so long as your DBA knows his stuff!). | |||
'''Before you start''', you must ensure the Virtual Centre is using a SQL Native Client driver to access the database (see [http://kb.vmware.com/kb/1003391 VMware KB1003391])... | |||
# Open up '''ODBC Data Source Administrator''', and go to the '''System DSN''' tab | |||
# Check that the driver you're using is '''SQL Native Client''' | |||
# If not, you'll need to upgrade... | |||
## Download from Microsoft and install SQL (see the VMware KB link above) | |||
## Stop your Virtual Centre Server service | |||
## Rename your existing DSN (eg append "old" to it) | |||
## Create a new DSN using the new driver but otherwise exactly the same as the previous (the name MUST be the same) | |||
## Restart the Virtual Centre Server service | |||
## Login using the VI Client and ensure everything looks good (clusters, ESX's, VM's, Alarms, Guest Customisations etc) | |||
'''To complete the migration...''' | |||
# Stop the Virtual Centre Server service | |||
# Backup the database (and log files) from your old SQL 2000 server | |||
# Restore the database (and log files) to your new SQL 2005 server | |||
# Ensure that your Virtual Centre's database account is the db_owner of the Virtual Centre database on SQL 2005 (as it was on the SQL2000 database) | |||
# Change the ODBC DSN settings on the VC server so it points to the SQL 2005 server (just change the server name) | |||
# Restart the Virtual Centre Server service | |||
# Login using the VI Client and ensure everything looks good (clusters, ESX's, VM's, Alarms, Guest Customisations etc) | |||
[[Category:VMware]] | [[Category:VMware]] |