vRealize Automation uses Microsoft SQL Server on Windows Server as the database management system (DBMS) to store data for the vRealize Automation IaaS components. The specific configuration of SQL Server for use in your environment is not addressed in this guide. High-level guidance is provided to ensure more reliable operation of your vRealize Automation deployment.
Review the vRealize Automation Support Matrix (PDF) for supported Microsoft SQL Sever versions for vRealize Automation.
To provide optimal performance for the vRealize Automation IaaS database, configure the Microsoft Windows Server virtual machine for Microsoft SQL Server with a minimum of 8 vCPU and 16 GB vRAM.
Microsoft SQL Server binaries should be installed in the operating system VMDK. Microsoft SQL Server, even if another drive is selected for binary installation, will still install components on the operating system drive. Separating Microsoft SQL Server installation files from data and transaction logs also provides better flexibility for backup, management, and troubleshooting.
Place Microsoft SQL Server data files (system and user), transaction logs, and backup files into separate VMDKs. For example:
- Operating System
- SQL User Database Data Files
- SQL User Database Log Files
- SQL TempDB
- SQL Backup Files
Utilize the VMware Paravirtualized SCSI (PVSCSI) Controller as the virtual SCSI Controller for data and log VMDKs. The PVSCSI Controller is the optimal SCSI controller for an I/O-intensive application on vSphere allowing not only a higher I/O rate but also lowering CPU consumption compared with the LSI Logic SAS. In addition, the PVSCSI adapters provide higher queue depth, increasing I/O bandwidth for the virtualized workload.
Use multiple PVSCSI adapters. VMware supports up to four (4) adapters per virtual machines and as many as necessary, up to this limit, should be leveraged. Placing operating system, data, and transaction logs onto a separate vSCSI adapter optimizes I/O by distributing load across multiple target devices and allowing for more queues on the operating system level. Consider distributing disks between controllers.
For more information, refer to the Architecting Microsoft SQL Server on VMware vSphere Best Practices Guide.