Submit a ticketCall us

Training Class Getting Started with SolarWinds Backup - February 28

This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup.
Register for class.

Home > Success Center > Network Performance Monitor (NPM) > Quick Orion database health check guide

Quick Orion database health check guide

Updated May 12th, 2016


This guide will help you address the most common questions and issues related to the Orion database performance check and configuration without using SolarWinds Database Administrator (DBA). 


This guide will help you address the most common questions and issues related to the Orion database performance check and configuration without using the SolarWinds Database Administrator (DBA). 

These questions include:

  • I have a very large Orion database. What should I check?
  • I have database performance issues. How can i improve my database performance?
  • Why do my Orion database tables have high fragmentation?  
  • Why is my Orion database growing so quickly?
  • Why does my Orion performance decrease each day? 
  • Why is my Orion Web Console loading data at a slow rate? 
  • How can I store a large number of Syslog and Trap files? 



Before you make any changes in your environment, create a full backup of your Orion database. See the SolarWinds video Backing Up, Restoring, and Migrating Your Orion Database for details. 

Checking your Orion database settings and configuration

The following questions provide links to resources that can help you resolve your database setting and configuration issues.

Managing your traps and Syslog files

How can I manage my traps and syslogs with a very large Syslog & Traps table in the Orion database?

SolarWinds Log & Event Manager is an optional security information and event management (SIEM) appliance for more demanding environments. The appliance uses logs for security, compliance, and troubleshooting. You can create and customize widgets to display critical events across your IT environment and monitor file activity for potential data theft.

Reclaiming database space

I have a large transaction file in the Orion DB, and my database is quickly losing space. What should I check?

You must check your default database retention settings. Any settings change can enlarge your database and impact performance in your SQL database server. 

After you complete these procedures, you must reduce your Orion Database size to reclaim free unused space in the database. This will reduce the database size and improve your database performance. 

Checking your SQL Server hardware 

Check the location of your Orion database file directories and ensure they are not stored on a single disk. 

Minimum SQL Server hardware requirements

The minimum SQL Server hardware requirement for a production environment is a 3GHz, Dual Core processor or better. This configuration is appropriate for all licenses.

Do not use less than a 2GHz processor for any Orion SQL database server.

RAID configurations

For best practice, configure your SQL database server components in a RAID configuration, as listed below.  

Component RAID configuration
Operating System 2X RAID 1 (Mirroring) disk
Database files

4X RAID 1+0 (Striping and mirroring) with separate partitions for the data and log files

Page file 2X RAID 1 (Mirroring) disk
Ad hoc components

SQL Server installed on virtual machines

Orion installations on VMware Virtual Machines and Microsoft virtual servers are fully supported if the minimum configuration requirements are met for each virtual machine. See "Requirements for Virtual Machines and Servers" in the Network Performance Monitor Administrator Guide for details. 


For more 

Reduce Performance Bottlenecks of Microsoft SQL Server Database. 

Please see SSD as recommended below. 

Microsoft SQL Server* on SSD Improving Database Performance


SolarWinds strongly recommends that you maintain your SQL Server database on a separate physical server. 

See Plan your production deployment for additional details. 


Last modified