Meet the database server prerequisites before installing the database server. The prerequisites listed here apply to any database you plan to install (for example, the Workspace ONE UEM or VMware Identity Manager databases).
SQL Server Hardware Requirements
The exact specifications needed for your SQL server depend on the size and needs of your deployment. Gather this information before proceeding so you size your servers correctly. Read the Workspace ONE UEM Recommended Architecture Guide, available at docs.vmware.com, for hardware sizing information and other technical details that ensure the smooth operation of your Workspace ONE UEM database.
SQL Server Software Requirements
Meet the following SQL Server software requirements:
SQL Server 2012, SQL Server 2014, SQL Server 2016, or SQL Server 2017 with Client Tools (SQL Management Studio, Integration Services, SQL Server Agent, latest service packs). Ensure the SQL Servers are 64-bit (OS and SQL Server).
Workspace ONE UEM does not support Express, Workgroup, or Web editions of SQL Server. These editions do not support all the features used in the Workspace ONE UEM application. Currently only Standard and Enterprise Editions are supported.
- Microsoft SQL Server 2012 Native Client 11.3.6538.0 is required to run the database installer. If you do not want to install Microsoft SQL Server 2012 Native Client 11.3.6538.0 on to your database server, then run the database installer from another AirWatch server or a jump server where Microsoft SQL Server 2012 Native Client 11.3.6538.0 can be installed.
- .NET 4.6.2 is required to run the database installer. If you do not want to install .NET on to your database server, then run the database installer from another Workspace ONE UEM server or a jump server where .NET can be installed.
- Ensure the SQL Server Agent Windows service is set to Automatic or Automatic (Delayed) as the Start type for the service. If set to Manual, it has to be manually started before database installation.
- You must have the access and knowledge required to create, back up, and restore a database.
When the database installer runs, it automatically updates your SQL Server with the latest versions of:
ODBC Driver 13 for SQL Server 64-bit
Command Line Utilities 13 for SQL Server 64-bit
Use TCP/IP to connect to the database and disable Named Pipes. In SQL Server Configuration Manager, navigate to SQL Server Network Configuration and select Protocols for MSSQLSERVER.
SQL Server AlwaysOn
The SQL Server AlwaysOn capability combines failover clustering with database mirroring and log shipping. AlwaysOn allows for multiple read copies of your database and a single copy for read-write operations.
For more information about AlwaysOn functionality, see https://msdn.microsoft.com/en-us/library/ff877884.aspx.
If you have the bandwidth to support the traffic generated by Workspace ONE UEM, the Workspace ONE UEM database supports AlwaysOn. The following AlwaysOn functionality has been tested for support:
- Database in an Availability Group
- Availability Group failover
- Secondary Replica promotion to Primary
To integrate SQL Server AlwaysOn, set up the following prerequisites:
Create a database listener to integrate with the Workspace ONE UEM Application and Database installations.
For more information on creating a database listener, see https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/create-or-configure-an-availability-group-listener-sql-server.
- If your AlwaysOn Availability Group uses different network subnets, you must configure your Availability Group Listener settings before you can deploy Workspace ONE UEM. Run the following commands using PowerShell on each database server in your cluster before you run the database installer:
>Get-ClusterResource <AG Listener Resource Name> | Set-ClusterParameter -Name HostRecordTTL -Value 60
>Get-ClusterResource <AG Listener Resource Name> | Set-ClusterParameter -Name RegisterAllProvidersIP -Value 0
For more information about HostRecordTTL values, including how to retrieve the AG Listener Resource Name, see https://blogs.msdn.microsoft.com/alwaysonpro/2014/06/03/connection-timeouts-in-multi-subnet-availability-group/.
Your database administrators decide the value for the HostRecordTTL. Low values result in a faster reconnection after a fail-over. For example, with a value of 60, the listener's DNS record updates take up to 60 seconds to match the IP address of the Primary (Active) SQL Node after a SQL fail-over.