Configuring the Instance Database Connection String and Pooling Options

You can configure the database connection string for either Windows Integrated Security or SQL Server encryption 2017, 2017 on Linux (Ubuntu), or 2019. It is recommended that you configure authentication with this database based on Microsoft’s recommended best practices for secure authentication to a database. Archer supports using Integrated Security for connecting to the database.

  • If using Windows Integrated Security, this option uses the current Windows identity established on the operating system thread to access the instance database. Selecting this option disables Login name and Password. Do not select this option if you are using SQL Server Authentication.
  • If using SQL Server encryption, you must install separate certificates on each server (web application, services, and database) and you must enable encryption on the SQL server. Otherwise the connection will fail.
  • If your application connects to an AlwaysOn availability group (AG) on different subnets, selecting the Multi-Subnet Failover option provides faster detection of and connection to the active server

Connection pooling is enabled for all instances and maintains a cache of database connections that you can reuse when requesting information from the database. Pooling reduces the number of new database connections that you must make.

On this page

Configure the instance database connection string

Complete this task for all configurations to set the database connection string for the instance.

  1. On the instance you are configuring, go to the Connection Properties section.

    1. Open the Archer Control Panel.
    2. From the Instance Management list, double-click the instance.
    3. Go to the Database tab, and then go to the Connection Properties section.
  2. In the SQL Server field, select the database server for the instance.
  3. Select the authentication method for connecting to the database server.

    Do one of the following:

    • If using Windows Integrated Security, select Use integrated security and skip to step 6.
    • If using SQL Server encryption, select Use encryption and continue at the next step.
    • If your application connects to an AlwaysOn availability group (AG) on different subnets, select the Multi-Subnet Failover option, and then continue at the next step. Enabling this option adds the following expression to the SQL connection string for the Instance database:

      • MultiSubnetFailover=True

  4. In the Login name field, enter the name of the SQL Server Authentication account.
  5. In the Password field, enter the login password for the SQL Server Authentication account.
  6. In the Database field, enter the instance database name.
  7. Click Test Connection to test the connection string.
  8. (Optional) In the Connection Timeout field, change the default duration of time for the connection timeout.
  9. Designate the file repository path.

Override the pooling options for the instance database

By default, database pooling is enabled with a minimum of 0 connections and a maximum of 100.

  1. Click the Database tab, and then go to the Pooling section.

    1. Open the Archer Control Panel.
    2. From the Instance Management list, double-click to expand the Instances list.
    3. Double-click the instance in the list that you want to configure.
  2. In the Pooling field, click Override connection pool size.
  3. In the Min pool size field, enter the minimum pool size.
  4. In the Max pool size field, enter the maximum pool size.
  5. On the toolbar, click Save.