Installing Microsoft SQL Server for i2 Analyze


If you are creating a production deployment, you can install SQL Server in any location. When you install SQL Server, record the location of the installation directory because you must specify this location in the deployment toolkit before you can deploy i2® Analyze.
If you are creating an example deployment, install SQL Server in the default location:
  • For Windows™: C:\Program Files\Microsoft SQL Server
  • For Linux®: /opt/mssql. Install the SQL Server tools in the default path: /opt/mssql-tools


In all deployments, you must ensure that the following features are installed or enabled:
  • Database Engine Services
  • SQL Server Authentication
  • TCP/IP protocol

In all deployments, you must install the ODBC Driver for SQL Server and sqlcmd utility on your database server.

On Linux:
You can also install Microsoft SQL Server Management Studio to administer your SQL Server installation. If you are using SQL Server on Linux, you can install SQL Server Management Studio on a Windows machine and connect to your SQL Server installation.

To create an example deployment on Windows, the instance name that you use must be MSSQLSERVER. Regardless of your operating system, the port number must be 1433.


You must have an SQL Server Authentication Login that has the following permissions:
  • Server Roles:
    • dbcreator
    • bulkadmin, to ingest the example data. The bulkadmin role is not supported on Linux.
  • User mappings for the msdb database:
    • SQLAgentUserRole
    • db_datareader
Note: In all scenarios, the user that you use to run the deployment scripts must have permission to create and modify the database.


  • Ensure that the SQL Server Agent service is running.
  • On Windows, if you want to use the instance name to connect to SQL Server ensure that the SQL Server Browser service is running.

Remote SQL Server database storage

If you plan to deploy i2 Analyze with remote database storage, you must install SQL Server on the database server, and SQL Server or Microsoft Command Line Utilities 17 for SQL Server on the application server. You can install SQL Server and the Command Line Utilities according to the previous instructions.

High availability

When you install SQL Server for HADR, you must ensure that the following statements are true:
  • All database servers are in the same IP address range.
  • All database servers are members of the same domain for SQL Server Always On Availability Groups DNS name resolution.
  • Two static TCP/IP addresses, one for the Windows Failover Cluster and one for the SQL Server Always On Availability Group. The IP addresses must be in the same range.
  • The same version of Windows Server is installed.

For information about installing SQL Server with SQL Server Always On Availability Groups, see Prerequisites, Restrictions, and Recommendations for Always On availability groups.