Comments
Sort by recent activity
I had written my own PowerShell script for automatic updates some time ago which worked flawlessly. After initially running it on on version 14, with the rebranding of the product name and paths, I found I needed to make a number of revisions to it to accommodate for the path changes. Not sure if you are having the same issue, but something to check. / comments
I had written my own PowerShell script for automatic updates some time ago which worked flawlessly. After initially running it on on version 14, with the rebranding of the product name and paths, ...
This problem did indeed seem to resolve with 13.0.48 and above. While I am not sure what was done to fix it, part of the issue identified is that with non-admin users it has to take the extra time to validate all of the groups defined in the the user configuration that it doesn't need to do for admin users. So likely somehow had to do with the extra time required and maybe something timing out. / comments
This problem did indeed seem to resolve with 13.0.48 and above. While I am not sure what was done to fix it, part of the issue identified is that with non-admin users it has to take the extra time...
I did install 13.0.45 Wednesday evening and turned enabled the SQLMONITOR_indexes setting. When I came in the next day, one of the base monitors had crashed. I also observed that some base monitors were maxed out at close to 100% CPU and memory utilization. I also observed very sluggish behavior when refreshing the SQL Monitor overview dashboard. In that all tiles would be hung up on loading for about 1 minute, which was too long for me, but I will acknowledge that it was an improvement over what it was before when the "Loading..." condition would not correct with previous versions. Still I felt compelled to disable the SQLMONITOR_indexes setting once again as I feel that the poor performance is not worth the feature. One observation and a suggestion is that in a multi-base configuration, if just one base monitor is acting up it brings everything down without providing any indication about which base monitor is the problem. So I would suggest that instead of hanging the whole multi-base dashboard up on "Loading...", it might help if it could move on and at least indicate which base monitor is causing the issue. / comments
I did install 13.0.45 Wednesday evening and turned enabled the SQLMONITOR_indexes setting. When I came in the next day, one of the base monitors had crashed. I also observed that some base monito...
Tom_C said:
Hi all,
Many thanks for your help and patience on this. Yesterday our development team released 13.0.44 aimed at addressing the high memory issues (from index sampling) and this can be downloaded here. Appreciate you may not be able to update immediately but once you have could I please ask you to remove the previously added environment variable, restart services and let us know if you believe this is looking stable again?
Unfortunately it's still an issue as I posted in the other thread. / comments
Tom_C said:
Hi all,
Many thanks for your help and patience on this. Yesterday our development team released 13.0.44 aimed at addressing the high memory issues (from index sampling) and thi...
Also see similar thread: https://forum.red-gate.com/discussion/90254/redgate-sqlmonitor-service-web-exe-consuming-99-ram-in-version-13-0-41 / comments
Also see similar thread:https://forum.red-gate.com/discussion/90254/redgate-sqlmonitor-service-web-exe-consuming-99-ram-in-version-13-0-41
On your base monitor host navigate to "Advanced system settings", select the advanced tab and click Environment Variables. [image] [image] [image] Then add the new system variable (under system variables not user variables) SQLMonitor_indexes and set it with a value of 0 [image] After that restart SQL Monitor Base Monitor [image] in services.msc Do that for all hosts that you are running SQL Monitor Base Monitor on. / comments
On your base monitor host navigate to "Advanced system settings", select the advanced tab and click Environment Variables. Then add the new system variable (under system variables not user variabl...
Thank you chrisqtran for confirming that the SQLMONITOR_Indexes system environment variable setting needs to be applied to the Base Monitor. I have now implemented that work around and will let you know if that resolves the stability issue for me. Let me give it a couple of days and if I don't need to restart SQLMonitor we will likely know. / comments
Thank you chrisqtran for confirming that the SQLMONITOR_Indexes system environment variable setting needs to be applied to the Base Monitor. I have now implemented that work around and will let y...
I believe I was able to answer my own questions via testing. The default behavior for 13.0.44 is to leave the indexes option disabled. As per documentation, one has to explicitly set the system environment to reenable the indexing feature. I went ahead and tested using on and off since that's what the documentation says to use. Though I suspect that 1 or 0 would work as well. Just note that I did not test with 1 or 0 for this release given that on and off work. Though I can confirm that a 0 value worked perfectly fine to disable the feature with version 13.0.42. And now for the stability question. Unfortunately it's still an issue. After setting the SQLMONITOR_indexes system environment variable on all hosts (both web and base) to a value of on and restarting the service for all hosts, I almost imediatly had the issue with the Overview page stuck on loading again. So I set the value for SQLMONITOR_indexes back to off and restarted once again. I don't want to discourage other users from testing the feature, which does need to be explicitly set, but my experience unfortunately was negative. / comments
I believe I was able to answer my own questions via testing.The default behavior for 13.0.44 is to leave the indexes option disabled. As per documentation, one has to explicitly set the system env...
So it looks like the 13.0.43 release notes, once published, sort of answered my question. In that 13.0.43 turns off the indexing feature by default. Instead it needs to be manually enabled if you want the feature and don't have stability problems with the product using it. Which for now I am fine with. Redgate team, once you identify the cause of the stability issue with the indexes feature and address it, please let us know so we can confirm. / comments
So it looks like the 13.0.43 release notes, once published, sort of answered my question. In that 13.0.43 turns off the indexing feature by default. Instead it needs to be manually enabled if yo...