Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Network Performance Monitor (NPM) > NPM Documentation > NPM 12.3 Administrator Guide > SolarWinds NPM requirements > NPM database server (SQL Server) requirements

NPM database server (SQL Server) requirements

Table of contents
Created by Lori Krell_ret, last modified by Magdalena.Markova on Jan 30, 2018

Views: 8,161 Votes: 9 Revisions: 13

Support for SQL 2008 and 2008 R2 is deprecated as of NPM 12.1. Future releases will no longer support using SQL 2008 or 2008 R2 as your database server.

The following table lists software and hardware requirements for your SolarWinds Orion database server using SolarWinds NPM license levels.

The Orion server and the SolarWinds Orion database must use separate servers.

If you install on a virtual machine, you must maintain your SQL Server database on a separate, physical drive.

As of Orion Platform 2018.2, you can use Amazon RDS as your database server.

Require-
ments

Small

SL100, SL250, SL500

Medium

SL2000

Large

SLX

XL (up to 400,000 elements. Monitoring over 12,000 elements requires additional polling engines.)

SQL Server

Express, Standard, or Enterprise versions of the following:

  • SQL Server 2012
  • SQL Server 2012 SP1
  • SQL Server 2012 SP2
  • SQL Server 2012 SP3
  • SQL Server 2012 SP4
  • SQL Server 2014
  • SQL Server 2014 SP1
  • SQL Server 2014 SP2
  • SQL Server 2016
  • SQL Server 2016 SP1
  • SQL Server 2017 (including installations on Linux)

Enterprise versions of supported SQL Servers:

  • 2012
  • 2012 SP1
  • 2012 SP2
  • 2012 SP3
  • 2012 SP4
  • 2014
  • 2014 SP1
  • 2014 SP2
  • 2016
  • 2016 SP1
  • 2017 (including installations on Linux)

Deprecation notice: Although you can use SQL Server 2012 with Orion Platform 2018.2 products, this version is deprecated and will not be supported on future versions of the Orion Platform. SolarWinds strongly recommends that you upgrade to Microsoft SQL Server 2016, 2017, or later at your earliest convenience.

Recommendations

  • Use 64-bit version of SQL Server.
  • Use the Simple database recovery mode to ensure best performance.
  • You can set the database recovery model to Full Recovery if your Orion Database is hosted on a SQL Cluster or if you use Always On Availability. However, you must back up your database regularly and ensure that volume you store your transaction log has free space that is at least equal to or greater than the size of your Orion database. Your transaction logs will continue to grow indefinitely until a database backup is performed and the transactions committed to the database. We recommend daily database backups when you use the Full Recovery model.
SQL Server collation
  • English with collation setting SQL_Latin1_General_CP1_CI_AS
  • English with collation setting SQL_Latin1_General_CP1_CS_AS
  • German with collation setting German_PhoneBook_CI_AS
  • Japanese with collation setting Japanese_CI_AS
  • Simplified Chinese with collation setting Chinese_PRC_CI_AS

We support CI database on an CS SQL Server.

We do not support case-sensitive databases.

CPU

Quad core processor or better

Dual quad core processor or better

Dual quad core processor or better

CPUs with a total combined PassMark score of 32,000 or higher

Hard drive space

20 GB minimum

40 GB recommended

50 GB minimum

100 GB recommended

100 GB minimum

400 GB recommended*

500 GB minimum

1TB recommended

 

Read/Write I/O performance of 30,000 IOPs

190,000 IOPS or better recommended

1 Gbit dedicated NIC

 

  • Due to intense I/O requirements, a RAID 1+0 drive is strongly recommended for the SolarWinds database, data, and log files with a dedicated drive for the server operating system and tempdb files.
  • Other RAID configurations can negatively affect your SQL Server's performance.
  • Mirrored drives for the OS and RAID 1+0 for database data files are recommended.
  • Solid state drives (SSD) are recommended for all components.

Some common files may need to be installed on the same drive as your server operating system. You may want to move or expand the Windows or SQL temporary directories. For more information, see Working with Temporary Directories.

Memory

SL100

4 GB minimum

8 GB recommended

16 GB minimum

64 GB recommended

64 GB minimum

128 GB recommended

256 GB minimum

512 GB recommended

SL250 & SL500

8 GB minimum

16 GB recommended

Authentication

Either mixed-mode or Windows authentication. If you require SQL authentication, you must enable mixed mode on your SQL server.

Other software

If you are managing your SolarWinds Orion database, SolarWinds recommends you install the SQL Server Management Studio component on your Orion server.

The Installation Wizard installs the following required x86 components if they are not found on your Orion database server:

  • SQL Server System Common Language Runtime (CLR) Types. Orion products use secure SQL CLR stored procedures for selected, non-business data operations to improve overall performance.
  • Microsoft SQL Server Native Client
  • Microsoft SQL Server Management Objects

* SolarWinds recommends the following hard drive configuration:

  • A hardware RAID Controller with a battery backed-up write back cache
  • Disk Subsystem 1 Array 1: 2x 146 GB 15K disks RAID 1 (mirroring) for the OS
  • Disc Subsystem 2 Array 2: 2x 146 GB 15K disks RAID 1 (Pagefile + Extra Storage)
  • Disk Subsystem 3 Array 3: with 6x 15k 146 GB or 300 GB disks configured in a RAID 1+0 array for your SQL MDF and FILEGROUPS.
  • Disk Subsystem 4 Array 4: with 4x 15k 146 GB or 300 GB disks configured in a RAID 1+0 array for your SQL LDF Transaction LOG file
  • Disk Subsystem 5 Array 5: with 4x 15k 146 GB or 300 GB disks configured in a RAID 1+0 array for your tempdb data file
  • Disk Subsystem 6 Array 6: with 4x 15k 146 GB or 300 GB disks configured in a RAID 0 array for your tempdb log file
Last modified

Tags

Classifications

Public