I am aware there are tons of posts on this subject. This my experience.
We started on 2020.2.6 a couple of years ago. When I arrived on the scene, the running app was so old it couldn't even be upgraded so we did a new install.
My App Server and DB Server are more than adequate and once I get everything configured we where running good and required minimum maintenance.
Recently we have been upgrading network hardware on a massive scale. Multilayer Switches, Access Points, Controllers.... hundreds and hundreds of devices....so theres that.
and syslog/traps are written to the database. I do not have an Syslog server.
I've always cruised along using about 300gig out of 400gig for the SW database. I noticed one day I need more so we added anther 100gig. It seemed stable and I'm so strapped for time we just let it go.
A couple weeks ago it rapidly went to 10gig. I beg the server guy to give me more before it crashed. Once he stopped crying about it 
he gave me another 100gig. It went through another 100gig in 6 hours. So I shut everything down.
Im sure you've figured out by now that my solarwinds knowledge is limited. I wear too many hats and SW is one of them.
I figured out pretty quick that syslog, traps and trapvarbinds are the tables that are to blame. It seems there are several devices among the new equipment that are sending a SNMP storm.
I have truncated and shrink'd those tables and gained a lot space back but my database it pretty hosed at this point. Too big to backup and I think I'm going to have to shrink the dat files as well.
or I could just start over. Wipe the database and redo the whole dam system. Extreme but it still might be world it.
Sorry for the book but I wanted to share and I do still have a question. I have traps and syslog services stopped for now. How can I limit the size of these three tables. (syslog, traps, trapvarbind) I know(think) it's in polling settings but it isn't making much sense.
