vRealize Automation uses a Microsoft SQL Server database to store information about the vRealize Automation IaaS elements and the machines that vRealize Automation manages.

Table 1. vRealize Automation SQL Database Design Decisions

Decision ID

Design Decision

Design Justification

Design Implication


Set up a Microsoft SQL server that supports the availability and I/O needs of vRealize Automation.

A dedicated or shared SQL server can be used so long as it meets the requirements of vRealize Automation.

Requires additional resources and licenses.


Locate the Microsoft SQL server in the vRealize Automation virtual network or set it up to have global failover available.

For simple failover of the entire vRealize Automation instance from one region to another, the Microsoft SQL server must be running as a VM inside the vRealize Automation application virtual network.

If the environment uses a shared SQL server, global failover ensures connectivity from both primary and secondary regions.

Adds additional overhead to managing Microsoft SQL services.


Set up Microsoft SQL server with separate OS volumes for SQL Data, Transaction Logs, TempDB, and Backup.

While each organization might have their own best practices in the deployment and configuration of Microsoft SQL server, high level best practices recommend separation of database data files and database transaction logs.

You might need to consult with the Microsoft SQL database administrators of your organization for guidance about production deployment in your environment.

Table 2. vRealize Automation SQL Database Server Resource Requirements per VM



Number of vCPUs



16 GB

Number of vNIC ports


Number of local drives


40 GB (D:) (Application)

40 GB (E:) Database Data

20 GB (F:) Database Log

20 GB (G:) TempDB

80 GB (H:) Backup

vRealize Automation functions

Microsoft SQL Server Database

Microsoft SQL Version

SQL Server 2012

Microsoft SQL Database Version

SQL Server 2012 (110)

Operating system

Microsoft Windows Server 2012 R2