This has been an ongoing issue for us, over 3 years now.
Here is the typical scenario. Some of my users start reporting sluggish results or long waits for SolarWinds results and they give me a call/email. I pop out to our 4 SolarWinds servers (Primary Poller, 2 x Additional Poller, 1 x Web Server) and check MSMQ folder size. Usually, one or more of the servers has a substantial MSMQ folder size... 1-2 GB in some cases. If nothing is done about this, SW will eventually flip out as MSMQ will die. I stop SolarWinds Services on the affected box, stop MSMQ, Delete the .mq files in the c:\Windows\System32\msmq\storage\ folder, restart MSMQ service, restart SW Services, system returns to normal operation, albeit with a gap in polling data for some nodes.
This happens enough that I have batch files created to check the MSMQ folder size and if needed, another to stop services and remote the files, then start services again.
I'm in a situation where I don't have any admin state on the SQL Server SolarWinds is hosted on and I have a feeling these issues are as a result of the SQL server being too overloaded and me getting blocking many times when trying to write the continual stream of data that SW polling generates.
How do I go about proving to the DB folks this is the issue, if it is in fact the issue? I'm more concerned in fixing this than blaming the SQL DB's... But when I've been on with SW support in the past, they are always surprised at how loaded the SQL server is with other databases.
I'm on NPM 12.1, SAM 6.3.0, NCM 7.6
We're on the latest MS SQL I believe and are on "Always On"
