Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Databases used by SolarWinds modules

Databases used by SolarWinds modules

Updated June 21, 2018

Overview

This page provides an overview of the types of databases used by SolarWinds modules.

Environment

  • All SolarWinds modules

Detail

SolarWinds products use the databases listed below:

SolarWinds Orion database

A Windows SQL server that should be hosted on a dedicated server in a production environment. It stores SolarWinds Orion configuration data and all collected performance and syslog data. For more information on deployment and system requirements, see the Orion Platform Administrator Guide.

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.

NTA Flow Storage database

A Windows SQL server for storing flow data. NTA 4.4 requires MS SQL Server 2016 SP1 or later version for the Flow Storage database. Please make sure you have an MS SQL 2016 database instance available for your installation.

SolarWinds supports two types of deployment for the NTA Flow Storage database:

  • Orion database and NTA Flow Storage database on one SQL server
    • The NTA Flow Storage database must be deployed on a SQL Server 2016 SP1 or later instance.
    • By default, the SQL Server 2016 SP1 Express edition is installed during express installation. You should consider changing the SQL server edition from Express to a higher one. For instructions, see Move the NTA Flow Storage Database to a different SQL server.

      Deploying the NTA Flow Storage database on SQL Server 2016 SP1 Express is not recommended in a production environment due to performance and other limitations. For more information about SQL server Express, see Editions and supported features of SQL Server 2016 (© 2017 Microsoft, available at https://docs.microsoft.com, obtained on February 20th, 2018).

      SQL_deployment2.png

  • Orion Database and NTA Flow Storage Database on separate SQL servers.
    • Orion Database running on SQL Server 2012 or later.
    • NTA Flow Storage Database running on SQL Server 2016 SP1 or later.

      SQL_deployment1.png

 

For more information, see NTA 4.4 System Requirements.

Log Manager for Orion (LM) database

A Windows SQL server for storing log data.  LM requires Microsoft SQL Server version 2016 SP1 or later
for the dedicated LM database. For more information, see the LM Installation Guide.

LM replaces the existing legacy syslog and trap services, but only provides a subset of the legacy functionality (no alerting or data migration). After installation of LM over the legacy syslog and trap services, the records remain in the database, but will not be used by LM. You can still access the read-only legacy records in the Syslog Viewer and Traps Viewer applications. All new syslog and trap messages will be stored in the dedicated LM database.

When installing and configuring SQL Server 2016 SP1 or later, enable full-text search to ensure optimum event log search performance in LM. You can still install LM and initiate event log searches without enabling this capability, but the speed and quality of your search may be significantly reduced.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.

 

 

Last modified

Tags

Classifications

Public