Network Management

SQL permission role requirements on the SolarWinds Orion Platform

This article will explain the SQL database permissions and roles needed in SolarWinds.

First published date

7/2/2019 12:59 AM

Last published date

2/23/2026 7:24 PM

Overview

SQL permission or role requirements depend on the scenarios that you are involved. The article will explain the necessary permission needed for different scenarios. 

 

Example Scenarios: 

  • Fresh installation of the SolarWinds Platform and at least one module 
    • NPM
    • SAM
    • NCM
    • IPAM
    • NTA, SRM, WPM, UDT, etc.

 

  • Adding a module or product to an existing SolarWinds Platform 
    • If you already have NPM and are adding SAM or NCM

 

  • An upgrade from one version to another version
    • If you are upgrading from 2019.4 to 2020.2, as an example
    • When upgrading to 2019.4 or 2020.2, you may be asked to install Log Analyzer, forcing you to create a new database and database user.
    • Installing version 2022.3 or later requires creating databases for Log Analyzer and Netflow Traffic Analyzer, if they don't already exist.

 

  • When running the Configuration Wizard after doing minor changes

Product section

Orion Platform

Resolution

 

Example Scenarios: 

  • If you are creating a new database:
    • As with a fresh installation or adding a product that needs to create a new database, like NTA or LA
    • The user account must be a member of the dbcreator server role. 
      • Note: The sysadmin role and the SA user account are always members of dbcreator

 

  • If you are using an existing database: 
    • As in upgrading an existing product, like NPM 2019.4 to 2020.2
    • 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 NPM: 
    • As with a fresh installation or installing a new product, like NTA or LA
    • The user account must be a member of the securityadmin server role.
      • Note: The sysadmin role and the SA user account are always members of securityadmin.

 

  • If you are using an existing SQL account: 
    • As when running the Configuration Wizard after minor changes are made
    • The user account needs only to be in the db_owner database role for the Orion NPM database.

 

  • In all scenarios, ensure that you have read permissions to the master database in SQL Server to perform the upgrade. 
    • The user account needs both VIEW SERVER STATE and VIEW SERVER PERFORMANCE STATE permissions enabled.

 

Note: It is essential to understand that if you are installing a new database, you will often be prompted to create a new user account, like in the installation of NTA or LA. In this case, you will need both the db_ownerdbcreator, and the securityadmin server roles to create the product user account and the new database.