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

My database has grown ENORMOUS!!!!

For some unknown reason my SQL 2005 NetPerfMon database has grown to a WHOPPING 163Gb the past 2 days. Needless to say it is killing me as I can't get backups of it, etc. and other issues with a bloated database.

I spent all day yesterday trying to find ways to shrink the database by prunning data, etc. I was running a query last night to delete all old syslog data but since my SQL server is so large it is taking forever to respond to any new queries. Yesterday the table size query told me that the largest tables were syslog and netflowsummary3 (I think).

If I run the compact command from Orion's database manager I eventually get a SQL error and then the database goes into recovery mode.

I am restarting the SQL service and will see what is what but need some assitance here.

Find more posts tagged with

Database

db_size

Accepted answers

All comments

Dean

I had the same issue - turns out it was McAfee. Do you have McAfee running? Try removing it and see if this helps.

Dean

FormerMember

Yes I have McAfee installed on the server however I need more details as to what is causing this as they won't just uninstall it w/o a valid reason. Any insight?

arronb

Ditto here..... I need help before it takes over! It doubled in size from 32 to 64 GB.

Yes we use McAfee, no I can't just uninstall it without a reason or expected fix time.

bshopp

You don't have to uninstall, but are you able to exclude the SolarWinds files from the scan engine? You can just remove the Orion directories from the scan.

FormerMember

We had a similar issue with the syslogs inflating the database. We finally re-evaluated what we "truly" needed syslogs from and then ported syslogs to thier own dedicated server so that it did not inflate NetPerfMon anymore.