To use a Microsoft SQL database for your vCenter Server repository, configure your database to work with vCenter Server.


You must create a database and user for vCenter Server. To simplify the process, you can use a script.


By using this recommended method, available with vCenter Server 5.x, the vCenter Server database administrator can set permissions for vCenter Server users and administrators to be granted through Microsoft SQL Server database roles.


If you use Microsoft SQL Server database, the simplest way to assign permissions for a vCenter Server database user is through the database role db_owner. Assign the db_owner role to the vCenter Server database user on both the vCenter and MSDB databases.


If you set database permissions by using the dbo schema and db_owner database role, you can use a script to create a vCenter Server user with the db_owner database role.


In this recommended method of configuring the SQL database, you create the custom schema VMW, instead of using the existing dbo schema.


You can create database objects manually with this method of configuring the SQL database.


After you create a vCenter Server user, establish a connection with a SQL Server database. This connection is required to install a vCenter Server system.


If the Microsoft SQL Server database has TCP/IP disabled and the dynamic ports are not set, the JDBC connection remains closed. The closed connection causes the vCenter Server statistics to malfunction. You can configure the server TCP/IP for JDBC.


vCenter Server Database Monitoring captures metrics that enable the administrator to assess the status and health of the database server. Enabling Database Monitoring helps the administrator prevent vCenter downtime because of a lack of resources for the database server.