Activity overview
Latest activity by cfendrick
Have you manually tested WMI connections from your base monitor to the server in question? There is documentation from Redgate on how to verify this here: Test the WMI Connection / comments
Have you manually tested WMI connections from your base monitor to the server in question? There is documentation from Redgate on how to verify this here: Test the WMI Connection
Processor(_Total)\% Processor Time Percent Processor Time tells us how busy the SQL server's CPUs are. It's a basic indicator to help us know that a SQL server is running well within acceptable operating parameters. Normally I'd expect to see this counter in the 20 to 50 percent range. When it jumps above 65-75% then I would start investigating. When it gets above 80% then I would get very nervous if you have been proactive and query tuning over the past weeks or months as that means that activity that require the processor are probably waiting for resources. It could be something as simple as out dated stats or one or more bad queries to simply large growth. The use of a SQL monitoring tool will help speed up this process so you are in the right place. / comments
Processor(_Total)\% Processor TimePercent Processor Time tells us how busy the SQL server's CPUs are. It's a basic indicator to help us know that a SQL server is running well within acceptable oper...
I would agree that this feature is not working in its current implementation. / comments
I would agree that this feature is not working in its current implementation.
Still not updated and shows the old version number in the post / comments
Still not updated and shows the old version number in the post
Start having someone look at DNS and all the NICs to see if something is IP'd wrong. Break out CMD and start doing some PING and NSLOOKUP to see how things resolve out. Good Luck and stay safe out there! / comments
Start having someone look at DNS and all the NICs to see if something is IP'd wrong. Break out CMD and start doing some PING and NSLOOKUP to see how things resolve out.Good Luck and stay safe out ...
SQL Monitor 8 released
Warning
No formatter is installed for the format not-found
This should actually say SQL Monitor 8.0.16 has been released. / comments
This should actually say SQL Monitor 8.0.16 has been released.
Did you check the box Delete all existing data for these servers from the Data Repository when you removed the Monitored servers?[image] / comments
Did you check the box Delete all existing data for these servers from the Data Repository when you removed the Monitored servers?
Are you able to see what your actual Failover Cluster name is and use that for the server you want to monitor? I know when I had to configuration one environment with what I like to call magical/nightmare things (dns alias or cname) and if I used anything other than the Cluster Name it would not work.... So while you are talking about AG groups I believe you would potentially want to look up what is in Failover Cluster Manager and potentially use the fully qualified domain name of what is listed there and that will hopeful pull in all the servers for you. Test that thing multiple times as when it pulls in the information it should all be GREEN and list all your servers. Also make sure the local windows firewall on each node has any needed ports open. As and example if you look at RedGates demo example site https://monitor.red-gate.com/ The Monitored server are really pulled in from the Cluster.[image]
[image]
Open up Failover Cluster Manager on one of the nodes and see what that FQDN name is and try that. [image] [image] / comments
Are you able to see what your actual Failover Cluster name is and use that for the server you want to monitor? I know when I had to configuration one environment with what I like to call magical/n...
Best practice is going to be install elsewhere and not on the SQL Server, ever. Disadvantages is that SQL monitor takes some resources and if the server is down then monitoring is down. In a high performance production scenario any and all resources should be dedicated to SQL. Only advantage and the typically use case for installing monitoring on the server itself is a cost saving measures in my opinion. It could also make for a smaller footprint by having 1 or 2 less VMs/Servers. / comments
Best practice is going to be install elsewhere and not on the SQL Server, ever. Disadvantages is that SQL monitor takes some resources and if the server is down then monitoring is down. In a high...