Create and configure the Microsoft SQL Server database for the vRealize Automation IaaS Components.
A supported version of Microsoft SQL Sever for vRealize Automation is installed per the vRealize Automation Support Matrix (PDF).
- The vRealize Automation service account has been added to Microsoft SQL Server with the sysadmin server role.
- Microsoft Distributed Transaction Coordinator has been configured.
- The Windows Firewall inbound access has been configured for Microsoft SQL Server (TCP port 1433) and the Microsoft Distributed Transaction Coordinator.
- Log in to the Microsoft SQL Server virtual machine as an administrative account by using a Remote Desktop Protocol (RDP) client.
- From the Start menu, click All Programs, click Microsoft SQL Server, and click SQL Server Management Studio.
Note: If Microsoft SQL Server Management Studio does not appear in your All Programs menu, the component might not have successfully installed. Verify that you have successfully installed Microsoft SQL Server Management Studio, and then continue with this procedure.
- In the Connect to Server dialog box, leave the default value of the Server Name text box, select Windows Authentication from the Authentication drop-down menu, and click Connect.
Note: During the Microsoft SQL Server installation, the Database Engine configuration wizard prompts you to provide the user name and password for the SQL Server administrator. If this user was not added during the installation, select SQL Authentication from the Authentication drop-down menu, and enter the user name sa in the User name text box, and the password sa_password in the Password text box.
- In the Object Explorer pane, right-click Databases and choose New Database.
- The New Database dialog box, select the General tab and enter the database name, for example, vRADB01.
- Set Database Owner to the same value as the service user name, for example svc-vra.
- Select the Options tab and configure the following settings:
- Set Recovery Model option to Simple.
- If using Microsoft SQL Server 2016 or 2017, set Compatibility Level as 100 or 120.
- Under Other options, change the Allow Snapshot Isolation option to true.
- Under Other options, change the Is Read Committed Snapshot option to true.
- Click OK.