I'm on 2k3 and sql 2005. Orion NPM 10.1.1 sp1, APM 3.5, and just added NTA 3.7.
My retention time is close to default. NPM polling is 2min/10min. Also have 5 min polling for APM.
Over 4 polling servers I have about 20,000 NPM elements, and though I don't know where I can see the exact count, about 3000-4000 APM elements. We've been running NPM for years so plenty of historical data.
Database (mdf) is about 13 GB. Database log (ldf) gets up to about 60GB. So yeah, at 10 days and only 3000 elements I think you can assume there's something wrong if your database is almost 150GB.
I had an issue about 2 years ago when there were a few machines that started sending out of control traps to my Orion server, and the traps and trapvarbinds tables exploded and nearly brought our whole Orion system down. At that time our database went from like 4 GB mdf and 15GB ldf to being over 100GB in just a few days. So I'd say look at the size of each table in your Orion database and see which ones are causing problems. May lead to to root issue.
Thank you very much lhorstma
It's exactly what is happening with us ( the traps and trapvarbinds tables ) are huge.
I am going to stop the SolarWinds Traps service until we find a better way to avoid that.
May I ask how did you solve it ?
I set up discard rules in the SW Trap config to get rid of the ones I didn't want before they hit the database. I think the main offenders for me were authentication traps and some out of control Blackberry traps. I then truncated the traps and trapvarbinds tables back to zero to start fresh.
Ok, me too I am planning to truncate the 2 tables.
Just wondering what traps did you keep, OIDs ?