Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Server & Application Monitor (SAM) > SAM Installation Guide > Prepare the SAM SQL database

Prepare the SAM SQL database

Table of contents
No headers


Updated: 5-5-2017

When installing SAM as a stand-alone product, you need to prepare a dedicated server for an SQL server. If you are installing SAM into an existing Orion Platform environment, you only need specific information to configure SAM to point to that database including the credentials and location.

The SolarWinds Orion database stores all monitoring data. Use these guidelines to configure the database before you install and configure SAM. If you need help installing the SQL Server database, refer to the guidelines provided by Microsoft.

Important: Install the SQL database on a dedicated server. You should not install it on the Orion server.

File:Success_Center/Reusable_content_-_InfoDev/SAM_Install_Guide/Reuse/0070-Install_SAM_evaluation/checkbox.gif Make sure the database and database server meet the system requirements. SolarWinds recommends following recommended sizing values for CPU, memory, and harddrive space.
File:Success_Center/Reusable_content_-_InfoDev/SAM_Install_Guide/Reuse/0070-Install_SAM_evaluation/checkbox.gif Ensure that you install the Orion database and the Orion Server on the same domain.

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, for example, #, %, or ^

For a new database, the user account must be a member of the dbcreator server role. The sysadmin role and the security administrator (SA) user account are always members of dbcreator.


For a new SQL account, the user account must be a member of the securityadmin server role. The sysadmin role and the security administrator user account are always members of securityadmin.

File:Success_Center/Reusable_content_-_InfoDev/SAM_Install_Guide/Reuse/0070-Install_SAM_evaluation/checkbox.gif For an existing database, the user account needs only to be in the db_owner database role for the existing database.

Set the recovery model of the database to Simple. SolarWinds does not support other methods.


Select SQL Server Authentication. SolarWinds Orion users use this method to access the SolarWinds Orion database.

SolarWinds recommends using SQL Server Authentication to ensure the SolarWinds Orion server can always access the SolarWinds Orion database, even when hosted remotely on a separate server.

File:Success_Center/Reusable_content_-_InfoDev/SAM_Install_Guide/Reuse/0070-Install_SAM_evaluation/checkbox.gif Helpful tip: After finishing your SAM installation and configuration, create a backup or snapshot of the database. If you encounter issues with further modifications or updates, you will have a working baseline of settings and data.

As you continue using Orion products, you should actively maintain and manage the Orion SQL database. See Best practices for managing your Orion database for tips, tricks, and maintenance recommendations.

Last modified