Comments
Sort by recent activity
This is often a result of the removal of the clustering roles not working properly. It's a known Windows issue. If removing and deleting the data then re-adding isn't working, rebuilding the cluster namespace can help. In an
elevated command prompt, can you please navigate to C:\Windows\System32\wbem, and run mofcomp.exe
ClusWMIUninstall.mof
then restart the
Windows Management Instrumentation service. Completely remove the server from Monitor and
then try re-adding it. / comments
This is often a result of the removal of the clustering roles not working properly. It's a known Windows issue.If removing and deleting the data then re-adding isn't working, rebuilding the cluster...
Hi, in terms of Azure offerings, Managed Instances are the closest in terms of capabilities, and so we licence RDS in the same way, ie a machine licence. This is unlikely to change in the near future. / comments
Hi, in terms of Azure offerings, Managed Instances are the closest in terms of capabilities, and so we licence RDS in the same way, ie a machine licence. This is unlikely to change in the near future.
SQL Monitor should alert on this - we collect the deadlocks from extended events and think that in this scenario the deadlock would appear as an event which therefore should in turn raise an alert. / comments
SQL Monitor should alert on this - we collect the deadlocks from extended events and think that in this scenario the deadlock would appear as an event which therefore should in turn raise an alert.
There actually... isn't, which we should probably add to the documentation! In the meantime here's the languages supported by the latest version: [image] [image] [image] [image] [image] [image] [image] [image] [image] [image] [image] We removed support for F# due to numerous problems with its accuracy, unfortunately. / comments
There actually... isn't, which we should probably add to the documentation! In the meantime here's the languages supported by the latest version:We removed support for F# due to numerous problems w...
It looks like this could possibly be a firewall issue: https://support.mozilla.org/en-US/questions/1280856. Have you setup the firewall on the new server in the same way as you had for the old server? Are you using an SSL? / comments
It looks like this could possibly be a firewall issue: https://support.mozilla.org/en-US/questions/1280856. Have you setup the firewall on the new server in the same way as you had for the old serv...
Sorry, what are you referring to when you mention Spotfire? / comments
Sorry, what are you referring to when you mention Spotfire?
Not yet, no but we will be releasing it shortly. / comments
Not yet, no but we will be releasing it shortly.
ANTS 11 is now available, which supports framework 5. / comments
ANTS 11 is now available, which supports framework 5.
Yes this is unfortunately normal behaviour with SSMS plugins. Some small patches won't require a reinstall but major/minor versions tend to. / comments
Yes this is unfortunately normal behaviour with SSMS plugins. Some small patches won't require a reinstall but major/minor versions tend to.
If connecting to an existing database, the installer doesn't need to access the model database, so I'm not sure why you would see that error if you connected the installer to an existing database, rather than chose the option to create a new one. The only requirement is listed here: https://documentation.red-gate.com/sm/installation-and-setup/planning-the-sql-monitor-infrastructure-and-installation/sql-monitor-database-requirements, under Using an Azure SQL Database. The installer needs to connect to an existing blank or existing SQL Monitor database is all, and the login has to either be the server admin or have a user on the master database as well, but only for the installer; for normal use, you only need the user on the specific azure sql db. It's possible that GCP does something different though, where is your basemonitor? We do only support GCP machines being monitored if the basemonitor is within the same network environment on GCP, due to issues with WMI queries running remotely in GCP. / comments
If connecting to an existing database, the installer doesn't need to access the model database, so I'm not sure why you would see that error if you connected the installer to an existing database, ...