Prerequisites for using external SQL Server

The configuration of the failover cluster with external SQL Server requires some additional steps. To learn about the general prerequisites for the failover cluster configuration, see Before you configure .

The failover server configuration with external SQL Server does not work in a workgroup environment.

Prerequisite	Description
Permissions for the SQL Server user	In Microsoft SQL Server Management Studio, add a Windows user to the public role and map the user to the db_owner database role for the following databases: Surveillance: Management and event server Surveillance_IDP: IDP Surveillance_IM: Incident Manager LogserverV2: LogServer
Connection to the SQL Server	Make sure that the VMS installations on the primary and secondary computers are connected to external SQL Server. If you want to change the SQL Server address after installing the VMS, you can do that from Windows registry. For more information, see the Maintenance section in the XProtect VMS administrator manual.
Service account	Make sure that the Management Server service on the primary and secondary computers is running under the Windows user you added on the SQL Server computer. If your SQL Server runs under a different user, you can change the account that runs the Management Server service. See Changing the service account that runs a VMS service.
Database conflicts	If you have two or more running management servers that are connected to the same SQL Server databases, your data might be corrupted. To avoid potential conflicts, before you configure the failover cluster, on the primary computer: Stop all VMS services. See Start or stop a VMS service. Stop all Internet Information Services (IIS) application pools for the VMS. See Start or stop an Internet Information Services (IIS) application pool. You must manually start the XProtect Management Server service and IIS application pools before you start the failover cluster configuration on the primary computer.