View Composer requires an SQL database to store data. The View Composer database must reside on, or be available to, the View Composer server host. You can optionally set up an Events database to record information from View Connection Server about View events.

If a database server instance already exists for vCenter Server, View Composer can use that existing instance if it is a version listed in the VMware Product Interoperability Matrixes at http://www.vmware.com/resources/compatibility/sim/interop_matrix.php. If a database server instance does not already exist, you must install one.

View Composer supports a subset of the database servers that vCenter Server supports. If you are already using vCenter Server with a database server that is not supported by View Composer, continue to use that database server for vCenter Server and install a separate database server to use for View Composer.

Important:

If you create the View Composer database on the same SQL Server instance as vCenter Server, do not overwrite the vCenter Server database.

For the most up-to-date information about supported databases, see the VMware Product Interoperability Matrixes at http://www.vmware.com/resources/compatibility/sim/interop_matrix.php. For Solution/Database Interoperability, after you select the product and version, for the Add Database step, to see a list of all supported databases, select Any and click Add.