The Update Manager server and Update Manager Download Service require a database to store and organize server data. Update Manager supports Oracle, Microsoft SQL Server, and Microsoft SQL Server 2008 R2 Express (64-bit).
Before installing the Update Manager server, you must create a database instance and configure it to ensure that all Update Manager database tables can be created in it. If you are using Microsoft SQL Server 2008 R2 Express, you can install and configure the database when you install Update Manager. Microsoft SQL Server 2008 R2 Express is used for small deployments of up to 5 hosts and 50 virtual machines.
To use Microsoft SQL Server and Oracle databases, you must configure a 32-bit system DSN and test it with ODBC.
Although you can install the Update Manager server only on 64-bit machines, Update Manager is a 32-bit application and requires a 32-bit DSN.
The Update Manager database you use can be the same as the vCenter Server database. You can also use a separate database, or you can use existing database clusters. For best results in a large scale environment, you should use a dedicated Update Manager database that is located on a different computer than the vCenter Server system database.
The Update Manager server requires administrative credentials to connect to the database. If the database user name and password change after you install the Update Manager server or UMDS, you can reconfigure Update Manager and UMDS without the need to reinstall them. See Reconfiguring VMware vSphere Update Manager.
Before you begin the database setup, review the supported databases. If you create an ODBC connection to a database server that is not supported, a DSN for the unsupported database might be displayed in the drop-down menu of the Update Manager installation wizard. For more information about the supported database patches, see VMware Product Interoperability Matrixes. If you do not prepare your database correctly, the Update Manager installer might display error or warning messages.