SQL monitors attached to the wrong instance.
When I attach SQL monitors to one instance of SQL server, they also attach themselves to the default instance of SQL as well, even if the default instance is not shown when adding the monitors.
It's making it very difficult to monitor the server, as the problems show up on both instances, even though they're only on one of them, and the thresholds can't be changed, as the other instance's monitor seems to overwrite the new threshold settings. For example, I change the threshold values and alert level on "SQL Cache Hit Ratio". I go back to edit it again, and it's back to the default values. :(
HELP!!
New to ADSelfService Plus?