Comments
4 comments
-
Hi Noah,
This is probably sampler information from the querywaitstats or query plan sampler, which is a known issue and we're working on reducing this. As a workaround though in the meantime you can edit the BaseMonitor config to reduce the frequency these are collected.
Is it possible for you to take a wireshark trace so I can just confirm this traffic? -
Yes, I can. What capture filter should I use? How long a time period should I capture? How do I send you results?
-
Hi, don't worry about the filter. You can send the trace into Support.
Incidentally though, if you haven't done so already you should upgrade to 7.0.13 before sending in the trace, as we've made some improvements to the samplers that help reduce network usage. -
7.0.13 now installed and doesn't seem to have changed the traffic. I put in a support ticket with the capture file.
Add comment
Please sign in to leave a comment.
Is this normal? Is there anything I can tweak to decrease the amount of traffic needed for SQL Monitor?
I'm using SQL Monitor 7.0.12.7831 monitoring MS SQL Server 2014 SP2 running on Windows Server 2012 R2. We currently only have a 100Mbps network so this is using a fairly significant percentage of our bandwidth.