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

Quick Orion database health check guide

Updated: July 11, 2018

Overview

This guide will help you address the most common questions and issues related to the Orion database performance check and configuration. 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? 

If you are using Orion Platform 2018.2 and later, check the Orion Deployment Health page and take the suggested measures.

See the Optimization Guide for further hints on how to optimize your deployment.

Steps

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. 

Step 1: Check the Orion database server properties 

See also Get to know your monitoring environment - Orion SQL database server properties.

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
Applications
Ad hoc components

Do not use SQL Server installed on virtual machines

SolarWinds does not recommend running an Orion database on a virtualized SQL server due to performance issues in case of larger installations. See SQL Server and Virtual Machines for more details.

Use SQL with SSD

For more demanding environments, SolarWinds recommends you to have the Orion SQL DB on SSD.  

Traditional Microsoft SQL Server database deployments required large data storage, typically composed of arrays of rotating hard disks drives (HDD) configured in a storage array network (SAN) over a network connection. 

As data volume increases, the database performance quickly degrades due to increasing I/O and network bottlenecks. 

Replace the slower HDD's with faster solid state drives (SSD) to relieve I/O bottlenecks and improves performance.

See Microsoft SQL Server* on SSD Improving Database Performance (2018 © Intel Corporation, available at https://www.intel.com/content/www/us/en/solid-state-drives/microsoft-sql-server-database-brief.html, obtained on July 11, 2018)

Use SQL on a dedicated server

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

See Plan your production deployment for additional details. 

Step 2: Check your Orion database settings and configuration

You can optimize your deployment by changing how often the data is polled, the time after which the detailed data is aggregated and summarized, and how long you need to keep historical data in the database.

Manage your traps and Syslog files

Reclaim database space

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

Step 3: Fine-tune SQL Server and database settings

See SQL Server Settings in SQL Server configuration best practices for NPM.

Last modified

Tags

Classifications

Public