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

SQL filegroup: restrict file growth?

I've created new file groups in SQL for the Netperfmon database called TRAPS and SYSLOG - and I've moved the corresponding tables into those filegroups. This has moved the bulk of the data out of the PRIMARY filegroup.

Does anyone know what Orion will do if I restrict the growth of these secondary SQL filegroups? I don't want traps and syslog data to grind monitoring to a halt, which has happened if the disk fills up. This has happens when a new device inadvertently sends massive numbers of traps/syslogs, or in a DoS situation. I want Orion to keep working in these situations.

Find more posts tagged with

Accepted answers

All comments

tdanner

Without having tested this scenario, my guess would be that the syslog and trap services would start failing to insert new data when they hit their limits. Since those are handled by independent services, I think it's unlikely to cause problems for other monitoring. This sounds like a promising solution to this problem.

sshuang68

When SNMP traps overloaded the database so it hit the size limit of 4GB (we run SQL 2005 Express), SolarWinds started generating lots of error messages. In just a few hours, the ERRORLOG file went from a few kilobytes to over 1GB. If your traps/SYSLOG has lots of useless messages, run a delete query to delete the unneeded traps/SYSLOG messages to control your database size.