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

NPM 10.3.1 and SQL 2005 Express 9

I recently upgraded to NPM 10.3.1 since I believe I had an issue with my database filling which caused the web console to crash. Anyway, I have only added a portion of my network to NPM and I already see an alert in the web console that the database is 80% full. I have limited the database retention in the web console to 30 days, syslog messages to 7 days and traps to 30 days. Am I missing something, I have no experience in SQL so I was thinking perhaps there's a setting on the database software that needs to change. I know my database is limited to 4GB and I don't understand how information such as syslog, traps and text in the database could be using close to 4GBs already. The version of database software is Microsoft SQL Server Management Studio Express 2005 version 9.00.2047.00 Thanks for any help! -Mark

Find more posts tagged with

Accepted answers

All comments

mharvey

Depending on the number of traps and syslog messages coming into your NPM setup, you could be getting a large amount of data. Also, note that much of the data may be free space in the database that the database still has, due to the change in data retention settings. Rather than working on removing data, as you may need it for reporting, you may want to think about upgrading SQL. If cost is an issue then I'd recommend upgrading to SQL Express 2008 which has a 10GB capacity. This may help with the issue with seeing your database at 80% full. Of course the overall fix for this would be to move from an express edition of SQL to full.

Regards,

Matthew Harvey

Loop1 Systems

http://www.loop1systems.com

markmattix

Thanks for your response Matthew. The database was completely deleted and recreated in mid-December so I'm not sure if the recent database retention settings I made would have removed that much data, if any.

markmattix

I just noticed this information in the web console:

1/9/2013 4:03 AM Indexes with fragmentation over 90% found during DB maintenance.

1/9/2013 4:02 AM Syslog reached 4235769 rows, which is above warning threshold of 1000000. For more information, see SolarWinds Knowledge Base.

mharvey

Index fragmentation is fairly common with the Orion NPM database. There are a number of methods to defragment the indexes, but it would be best handled by a DBA. The fact there are that many syslog messages means that you probably have a lot of devices sending, or several devices sending large amount, such as firewalls that have been configured to send everything. I would look at seeing what is needed from these and either update the configuration to only send the needed severities, or create a rule that drops the unneeded ones that come in.