Vcenter Server Database Patch And Configuration Requirements - VMware ESX 4.0 - UPGRADE GUIDE UPDATE 1 Update Manual

vSphere Upgrade Guide
To use a newly supported SQL database, such as Microsoft SQL 2008, you do not need to perform a clean
n
installation of vCenter Server if your existing database is also Microsoft SQL Server. For example, you can
upgrade a Microsoft SQL Server 2000 database to Microsoft SQL Server 2005 or Microsoft SQL Server 2008
and then upgrade VirtualCenter 2.x to vCenter Server 4.0.
If you are upgrading from VirtualCenter 2.0.x and you are using the previously bundled demonstration
n
MSDE database, you must perform a clean installation of vCenter Server. VirtualCenter 2.0.x with the
demonstration MSDE database has no supported upgrade path to vCenter Server 4.0.
If you are upgrading from VirtualCenter 2.5 with the bundled SQL Server 2005 Express, you do not need
n
to perform a clean installation of vCenter Server.
If you have a Microsoft SQL database and you are upgrading from VirtualCenter 2.0.x, make sure that
n
bulk logging is enabled. You can disable it after the upgrade is complete.
If you have a Microsoft SQL database, your system DSN must be using the SQL Native Client driver.
n
Make sure that the database user has the following permissions:
n
n
Oracle
n
Microsoft SQL Server
Also review
n

vCenter Server Database Patch and Configuration Requirements

After you choose a database type, make sure you understand the configuration and patch requirements for
the database.
N vCenter Update Manager also requires a database. VMware recommends that you use separate
OTE
databases for vCenter Server and vCenter Update Manager.
If your VirtualCenter 2.x database is not supported for upgrade to vCenter Server 4.0 Update 1 and later, first
upgrade your database (or import your database into a database that is supported for upgrade to vCenter
Server) and then upgrade vCenter Server.
42
Either assign the DBA role or grant the following permissions to the
user:
grant connect to <user>
grant resource to <user>
grant create view to <user>
grant create any sequence to <user> # For upgrade from VC 2.0.x
grant create any table to <user> # For upgrade from VC 2.0.x
grant execute on dbms_lock to <user> # For upgrade from VC 2.0.x/
2.5
grant unlimited tablespace to <user> # To ensure sufficient
space
After the upgrade is complete, you can optionally remove the following
permissions from the user profile: create any sequence and create any
table.
By default, the RESOURCE role has the CREATE PROCEDURE,
CREATE TABLE, and CREATE SEQUENCE privileges assigned. If the
RESOURCE role does not have these privileges, grant them to the
vCenter Server database user.
Make sure that the database login has the db_owner fixed database role
on the vCenter Server database and on the MSDB database. The
db_owner role on the MSDB database is required for installation and
upgrade only. You can revoke this role after the installation or upgrade
process is complete.
"Database Scenarios," on page 43.
VMware, Inc.