December 5, 2021 at 7:12 pm
Hi Everyone,
I'm also experiencing the issue of a constantly "paused" SSMS Activity Monitor on a recently setup server.
I've followed all the steps outlined in this blog post, without success: https://bobcares.com/blog/ssms-activity-monitor-paused/
I'm using SQL Serer 2019 v15.0.4188.2 with SSMS v18.10.
I've tried remote connections, local connections, using the "sa" user as well as another user with sysadmin permissions.
I've also tried all of this with windows authentication and with SQL Server Authentication. As I'm using the highest-privilege user on the windows server as well as the sa user, I don't really see how this could be a permission problem.
Help would be greatly appreciated =)
December 6, 2021 at 5:25 pm
Have you tried unpausing it?
Personally, I am not a big fan of activity monitor. It shows information in one nice dashboard, but even some Microsoft employees recommends against - https://redmondmag.com/articles/2021/08/25/activity-monitor-sql-server-performance.aspx.
I would much rather use a monitoring tool to monitor my databases, but that is just me.
As I am assuming you have already tried all of the tricks on that page you linked, I would do the next logical step - check the logs. The logs will almost always tell you what is wrong. I would check the SQL logs as well as the Windows logs as it could be in either of them.
99.99999% of the time, when an error occurs, the logs are a good and safe thing to check and will almost always point you in the right direction.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
December 7, 2021 at 6:08 pm
If the activity monitor is pausing after a timeout - you probably have run into a bug with the code provided by Microsoft to populate the data. There is a known issue where this becomes a problem when there are too many objects in the system being monitored.
There is no fix - but I did provide a code update to MS, but they moved everything around so I can't find the original issue.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply