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 Table 1. For example, View Composer can use the Microsoft SQL Server instance provided with vCenter Server. 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.
The following table lists the supported database servers and versions as of the publication date of this document. 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.
| Database | Service Packs/Releases | Editions |
|---|---|---|
| Microsoft SQL Server 2014 (32- and 64-bit) |
No SP, SP1 | Standard Enterprise |
| Microsoft SQL Server 2012 (32- and 64-bit) |
SP2 | Express Standard Enterprise |
| Microsoft SQL Server 2008 R2 (32- and 64-bit) |
SP2, SP3 | Express Standard Enterprise Datacenter |
| Oracle 12c | Release 1 (any release up to 12.1.0.2) | Standard One Standard Enterprise |
