Comments
Sort by recent activity
I can confirm that the problem appears to be fixed after updating to 14.0.45. / comments
I can confirm that the problem appears to be fixed after updating to 14.0.45.
Thanks Alex. I'll update right away and confirm shortly. / comments
Thanks Alex. I'll update right away and confirm shortly.
This error happens if there is blocking data to display within the time window. I doubt that's the issue, because this problem manifested itself on all base monitors after applying the upgrade. And doesn't the query folder have more to do with collecting queries from procedure cache as opposed to active processes? Anyway as stated in another thread this is reproducible in your live DEMO, so please fix it there and provide an update that addresses the issue. / comments
This error happens if there is blocking data to display within the time window. I doubt that's the issue, because this problem manifested itself on all base monitors after applying the upgrade. A...
Actually, I may be wrong that Blocking is the trigger, but here is another link to Redgate's Live Demo that duplicates the issue: ssc-db-n3\(local) - Server Overview / comments
Actually, I may be wrong that Blocking is the trigger, but here is another link to Redgate's Live Demo that duplicates the issue:ssc-db-n3\(local) - Server Overview
@FTP2It, they just released 14.0.45 and this fixed it for me. / comments
@FTP2It, they just released 14.0.45 and this fixed it for me.
The issue happens if it needs to display blocking information in the time window selected. It's a bug that Redgate needs to fix. / comments
The issue happens if it needs to display blocking information in the time window selected. It's a bug that Redgate needs to fix.
I'm getting that too on 14.0.44. I made another post before noticing this one. I was able to reproduce the error on Red-Gate online demo as well. I observed that sometimes it occurs when setting a larger timeline range. Like 5 hours or so. Redgate, please pull the logs from your own online demo. You should be able to reproduce it by clicking the link below: https://monitor.red-gate.com/overviews/SQLMON-EC2-BM2/dbms/r1,4:base,s36:260ca7e9-c6fa-4cc5-8de2-e05e68114e71,7:Cluster,1,4:Name,s21:ssc-db-clus.ssc.local,9:SqlServer,1,4:Name,s10:ssc-db-n3\,?zoom=1738282603991,1738308365189&timeRange=12&maxTime=1738308365189 / comments
I'm getting that too on 14.0.44. I made another post before noticing this one.I was able to reproduce the error on Red-Gate online demo as well. I observed that sometimes it occurs when setting a...
I can confirm that 14.0.8 fixed the issue. Thanks Alex. / comments
I can confirm that 14.0.8 fixed the issue. Thanks Alex.
In playing around with this, I have discovered that the issue is not so much the user role that but instead the groups that an individual AD login or AD group has access to. It seems that if I give the AD user or group access to monitor all Redgate monitored servers, then the user can access the metrics of the individual server. This is not an ideal workaround. We need Redgate to fix whatever it was that they broke going from 14.0.6 to 14.0.7. Need an emergency 14.0.8 release that addresses that change! / comments
In playing around with this, I have discovered that the issue is not so much the user role that but instead the groups that an individual AD login or AD group has access to. It seems that if I giv...
Always accompany new releases with a rollback script to counteract any breaking bugs that may be introduced. Resorting to restoring the RedGate monitor database to a state prior to the upgraded release is suboptimal, as it results in the loss of captured data. The ideal solution would be to facilitate the redeployment of an older version, wherein the version history and table changes in the database are reinstated, allowing for the reapplication of older binaries. This process should mirror the functionality of tools like SQL Compare and SQL Data Compare, which can manage key tables effectively. / comments
Always accompany new releases with a rollback script to counteract any breaking bugs that may be introduced. Resorting to restoring the RedGate monitor database to a state prior to the upgraded rel...