nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

database size

davidn

I am having database size problems with my Orion database. i have had the system in place since mid-January 2007 and i am monitoring 74 nodes and 790 interfaces. Our database kept growing at was at 80GB as of last night. I tried running the compact database process and it locked up overnight and now the database is 116GB. I have 2 questions:

1. Why did the compact process increase the database size, and how can I correct this?

2. What size are some of your databases? I just think 80GB is way too big for what i am monitoring. I would expect that there are some companies that monitor more systems and have a smaller database. Just let me know some things you guys do to manage database size.

Thanks.

Find more posts tagged with

Accepted answers

All comments

chris.conway

Which of the modules do you have installed?

Applicaiton Monitor
Wireless Monitor
NetFlow

Are you using Orion to receive SNMP Traps or Syslog messages?

davidn

I am not using any of those modules. I am receiving SNMP traps and Syslog messages, although i have just recently started collecting syslog messages.

I am running a SQL process to shirnk the database size and think I can get it back to what it was. I guess my main question is if 80GB is a normal size for an Orion db that has been running for almost 6 months, considering the amount of nodes that I am monitoring.

jtimes

What version of Orion are you on? Are you running Cirrus on that server?

Prior to going to v8.1 I ran the manual table compact/re-index via the db manager once a month, but my DB never got that large. Even with your number of elements, the DB should not be that large! Unless you are retaining Detailed and Hourly Stats forever...

Here are my stats:

Data Space Used: 9.6Gbytes

Index Space Used: 3.1Gbytes

Network Elements	19324 Elements
Nodes	6700 Nodes
Interfaces	12541 Interfaces
Volumes	83 Volumes

Retain Detail Stats	7 Days
Retain Hourly Stats	30 Days
Retain Daily Stats	60 Days
Retain Events	30 Days

davidn

I just upgraded to 8.1. I was on 8.0 previously. I am not running Cirrus. I will look at my settings and compare them to yours after the database task is finished.

jtimes

David,

Are you running native SQL maintinence, instead of using the Database Manager from the Orion server?

davidn

I am using the SQL maintenance right now. Everytime I tried to use Database Manager, it would lock up.

jtimes

On an off note: Just how many DAYS did it take to run the Configuration Wizard when you upgraded to v8.1?

darryld

In my experience it is not the database as a whole which increases in size but one table. As you are collecting traps check the size of the trapvarbinds table.

You may need to restrict the number of traps you are receiving or us the "discard" action to limit the number which are stored in the database

FormerMember

Have you had problems with the 8.1 database manager?