Comments
Sort by recent activity
ANTS 11 is now available, which supports framework 5. / comments
ANTS 11 is now available, which supports framework 5.
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...
No I don't think so. I'll forward this on to the .net team now. / comments
No I don't think so. I'll forward this on to the .net team now.
With some basic analysis, it looks like we have some instrumentation specific for MySQL. I've not actually got the ability to test with MariaDB so really I'd just give it a go using normal sql profiling: https://documentation.red-gate.com/app/setting-up-and-running-a-profiling-session/profiling-sql-queries. I would expect the calls to show up here as they would with sql/oracle. / comments
With some basic analysis, it looks like we have some instrumentation specific for MySQL. I've not actually got the ability to test with MariaDB so really I'd just give it a go using normal sql prof...
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.
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.
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...
This custom metric might help https://sqlmonitormetrics.red-gate.com/percentage-of-free-log-space/ if you mean an alert for log size. You can then setup an alert email for that custom metric. / comments
This custom metric might help https://sqlmonitormetrics.red-gate.com/percentage-of-free-log-space/ if you mean an alert for log size. You can then setup an alert email for that custom metric.
The mentioned attribute is the easiest way to detect that it was obfuscated by SA. I think that there will be always some footprint that can track down which obfuscator was used. That's because each obfuscator uses different techniques to obfuscate assembly and because of this, if you analyse the output, the application would be obfuscated in a way that is specific to obfuscator. As you said, some obfuscation methods are irreversible like obfuscating the names. There are also some obfuscation that will be always reversible and we can only make them harder to reverse like obfuscation of strings in the application (we can make it hard to analyse but in the end the application will have to resolve them in run-time, so if the application can get them then any de-obfuscator can simulate what an application will do in run-time and get this string also). If you are worried then, unfortunately, there is always the possibility of reversing some forms of obfuscation and for .NET applications, for someone that knows what they are doing it is not that hard to analyse even the obfuscated assembly. / comments
The mentioned attribute is the easiest way to detect that it was obfuscated by SA. I think that there will be always some footprint that can track down which obfuscator was used. That's because eac...