Submit a ticketCall us
Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > MS SQL support for MultiSubnetFailover=true

MS SQL support for MultiSubnetFailover=true

In Orion Platform 2017.1 and earlier versions, you need to use MS SQL to enable Orion with MultiSubnetFailover=true in the connection string.

To enable this parameter, you need to manually modify the Orion database connection string.

Without this connection string parameter to the database, the connection times out and will not complete.

Environment

Orion Platform 2017.1 and earlier

Starting with Orion Platform 2017.3, Orion Platform products, such as NPM 12.2, support SQL AlwaysOn Availability Groups in a MultiSubnet Failover configuration.

Detail

In Orion Platform 2017.1 and earlier, there is no configuration or connection attribute that is officially supported.

Orion Database Authentication and requirements 

When you are configuring the SolarWinds Orion database, you are required to select the authentication method used by the NPM user to access the selected SolarWinds Orion database. In general, SolarWinds recommends that you use SQL Server Authentication to ensure that the Orion server can always access the SolarWinds Orion database, even when it is hosted remotely on a separate server.

  • The selected SQL Server instance must support mixed‑mode or SQL authentication with strong passwords.
    A strong password must meet at least three of the following four criteria:
    • Contains at least one uppercase letter.
    • Contains at least one lowercase letter.
    • Contains at least one number.
    • Contains at least one non-alphanumeric character, e.g., #, %, or ^.
  • If you are using SQL Express, specify your instance as (local) and use a strong password. Due to its inherent limitations, SolarWinds recommends that you do not use SQL Express in production environments.
  • If you are creating a new database, the user account must be a member of the dbcreator server role. The sysadmin role and the SA user account are always members of dbcreator.
  • If you are using an existing database, the user account needs only to be in the db_owner database role for the existing database.
  • If you are creating a new SQL account for use with Orion Platform products, the user account must be a member of the securityadmin server role.
    The sysadmin role and the SA user account are always members of securityadmin.
  • If you are using an existing SQL account, the user account needs only to be in the db_owner database role for the SolarWinds Orion database.


See the SQL server requirements for the latest Orion Platform version.

 

 

 

 

Last modified

Tags

Classifications

Public