We have had ongoing issues with database maintenance(cases have been opened) with NPM version 12.01.
1)We are running SQL 2014 on a Windows 2012 R2 server - 64 bit o/s.
2)The recommended steps by support are to lower database retention rates on:
3)Our customer needs to keep the retention settings. We typically end up truncating the table - "Custompollerstatistics_detail"; then repeat database maintenance. This table hits large row size:
|table||rows||data size||index size||unused|
|CustomPollerStatistics_Detail||695588513||105442344 KB||91436616 KB||43344 KB|
4)Another recommendation is moving to a physical server. We have run I/O reports on other SQL servers and we have several other SQL servers of the same size(non Solarwinds); that are running on VM's.
Just wondering if anyone else is facing this issue and what they are doing to resolve it.
I found some other threads - DB Maintenance - How to Handle It When Some Tables Have Tens of Millions of Rows?
We had a similar problem with our 2nd instance a few months ago and it was due to the traps table(which we have since turned off traps). After we truncated this table we haven't had any problems since that time.