VMware vCloud Director – Database Setup – Part 1

VMware vCloud Director Database Setup

In this first part of a series of VMware vCloud Director tutorials, we look at creating the vCloud Director database on our Microsoft SQL Server.

Before you start you will want to check on the VMware compatibility list to see what version of Microsoft SQL Server are compatible with the version of vCloud Director you are using.

You can check the VMware Product Interoperability Matrix by clicking here, select the Solution/Database Interoperability tab. In the first drop down box select VMware vCloud Director followed by your version on the right. In the second drop down box select the version of Database you wish to use. This will then produce a table letting you know what platform is supported and what is not.

Creating a vCloud Director Database

1. Open Microsoft SQL Server Management Studio. Within object explorer on the left hand side, right click on Databases and select New Database. I’m going to set my database name as vcloud6 and ensure that my Initial Size (MB) column is 100 for the database and 1 for the log

2. Click on Options and change the collation to Latin1_General_CS_AS. Click Ok and the database will be created.

3. Next we want to change a few settings within the new database. To do this we need to run a query by clicking on the New Query button at the top left hand side of the screen. Once the query window has opened type in the exact query as seen in the screen shot below. Lastly click on the !Execute button.

4. We will now create the database user account. In my setup I will create a user called vcloud6db, enter in the password, untick enforce password policy and set the Default Database to vcloud6

5. Click on User Mapping. Place a tick next to the vcloud6 database and ensure db_owner is selected within the Database role membership window. Click Ok and the user will be created.

Disclaimer:
All the tutorials included on this site are performed in a lab environment to simulate a real world production scenario. As everything is done to provide the most accurate steps to date, we take no responsibility if you implement any of these steps in a production environment.