Preparing SQL Server for HADR

To deploy i2 Analyze with HADR for the Information Store database, SQL Server must be configured to be part of an availability group.

Ensure that SQL Server is installed correctly for Always On availability groups. For more information, see Installing Microsoft SQL Server for i2 Analyze.

If you are using Microsoft SQL Server Standard edition, you can use basic availability groups only. For more information about basic availability groups, see Always On Basic Availability Groups.

To configure SQL Server for high availability, you add your database servers to a fail over cluster and then add any database instances to an Always On availability group.

On Windows, use Windows Server failover clustering to create a cluster of servers to host your SQL Server instances. For more information, see Failover Clustering in Windows Server.

On Linux, use Pacemaker to create the server failover cluster.

If you are deploying SQL Server on Windows, complete the following steps.
  1. Install the Windows Failover Clustering feature on each of the servers that will be in your SQL Server Always On Availability Group and create a failover cluster.

    For more information, see Create a failover cluster.

    For i2 Analyze, the failover cluster must use a static IP address.

  2. Create and configure an Always On availability group.
    For more information, see Reference for the creation and configuration of Always On availability groups
    1. Enable Always On availability groups on each database server.
      For more information, see Enable the Always On availability group feature for a SQL Server instance.
    2. Create an Availability Group on the primary SQL Server instance.
      For more information, see Use the New Availability Group Dialog Box (SQL Server Management Studio).

      • Set Required synchronized secondaries to commit to 1.

        Set it to 0 if you are using Basic availability groups.
      • Select Database level health detection.
      • Do not specify any Availability Databases now because the Information Store database does not exist.
    3. Create an availability group listener for the availability group.
      For more information, see Configure a listener for an Always On availability group.
      Use a static IP address for the availability group listener. When you configure i2 Analyze to connect to a remote Information Store database, you specify the hostname and port number of the Availability Group Listener.
If you are deploying SQL Server on Linux, complete the following steps.
  1. Deploy a Pacemaker cluster.
    For more information, see Deploy a Pacemaker cluster for SQL Server on Linux.
  2. Create and configure an Always on availability group and the Pacemaker cluster.
    For more information, see Create and configure an availability group for SQL Server on Linux.
    • Set cluster type to EXTERNAL
    • In Select Databases, do not select any databases because the Information Store database does not exist.
    • In Specify Replicas, create an Availability Group Listener. When you create the availability group listener, use a static IP address. When you configure i2 Analyze to connect to a remote Information Store database, you specify the hostname and port number of the Availability Group Listener.
    • When you create the IP address resource for the availability group, use the same IP address as the Availability Group Listener.
Deploy i2 Analyze and the Information Store database. For more information, see Deploying i2 Analyze with high availability.