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 > Determine the Orion SQL database size

Determine the Orion SQL database size

Table of contents

Overview

This article discusses how to determine the space to allocate for the Orion SQL database.

Environment

All Orion Platform versions

Detail

There is no fixed formula to determine how much space to allocate for the Orion SQL database. SolarWinds recommends a 30-day evaluation of your environment to observe the growth of your database, and then adjust the retention settings. 

The database size depends on the number of the following:

  • Nodes, interfaces, and volumes you are polling.
  • How much traffic is going through the devices, your retention setting for statistical polling.
  • Syslog messages (if you receive them and how much you are receiving).
  • Trap messages (if you receive them and how much you are receiving).
  • Retention settings for syslogs/trap messages.
  • NetFlow (95% Top Talker? DNS? IpAddressLookup?).
  • Wireless, UnDP, hardware health and other modules.


If you have a full SLX with NetFlow, Syslog, Traps for seven days retention, a rough guide is to assign an approximate of 10-50 GB to the Orion database.

There are many posts on the topic Database Sizing on THWACK that you can review to decide about your database sizing.

 

Last modified

Tags

Classifications

Public