Configure high availability for xConnect
If you are deploying a PaaS solution or if you are not going to configure a High Availability feature, skip this section.
High Availability is an xConnect feature that is based on Always On availability groups and configurable retryers.
Configure Always On availability groups
A Windows Server Failover Cluster (WSFC) is required when you deploy Always On availability groups.
You must also configure Synchronous-commit mode with automatic failover.
For more information about how to configure availability groups, see Microsoft’s documentation.
To provide client connectivity to the database for a given availability group, you must create an availability group listener.
The availability group listener allows a client to connect to an availability replica without knowing the name of the physical instance of SQL Server that it is connecting to. You must specify the DNS name of the listener in the connection string instead of the server name. This helps your solution to automatically switch to the primary replica during a failover.
Here is an example of a connection string for an availability group listener:
Configure the Collection database
The Collection database is designed to manage high read/write activity, and therefore supports sharding. The catalog of all the shards is located in the Shard Map Manager database. You must manually update the [ShardsGlobal] table in the catalog so that it can use listeners instead of server names.