Comments
-
@"cpriddy" Thanks, I guess that answers one question. I had already read the above-mentioned KB articles, as they were obviously the inspiration for this thread. Since they both contain the CURSOR code for looping through the existing databases, I guess that means that the requirement to touch each database in SQL 2012…
-
@"darichar" (or @"[Deleted User]" or anyone else) any updates on this, esp. wrt. DPA 2020.2? I hope a better way has been found for SQL Server 2012 instances. The support articles I found still have the same basic suggestion. Just seems odd to recommend a method that obviously becomes stale as soon as you add a new…
-
+1 above. And we did try the offline installer. From our Customer Portal home page, went to the "Hot Fixes" tab, the first item says that it's HotFix2, offline installer. I downloaded that and ran it, and get the same message, that all products are already up to date. But we haven't installed any SW updates to this server…
-
Actually, we're doing AG for both redundancy and load. But we have a few apps that don't "play well" with AO, so a failover alert to let us know when to tend to those apps would be helpful. And thanks for the reminder about the "not visited since normal" idea; I forgot that was an option. Time to go play......
-
Thanks samr33 , that's similar to what I've been toying with. We have some AO instances where we intentionally put some listeners on one node, some on the other. But I can join to sys.availability_group_listeners and select on the listener name to be more selective. The challenge I'm finding is to have it alert only when…
-
Okay, 11.0 is here, like the shiny new interface, and the added Always-On info is good. But what about alerting? We'd like to set up alerts for when Availability Groups fail over from one replica to another. An Alert Type, under Adminstrative, something like "Availability Group Status Change". I suspect I could write a…
-
Any update on this? This seems like a yawning gap in manageability. There should be a navigation something like this: * Node -> Manage node -> Enable/disable alerts on THIS node I should be able to continue managing a device, collecting stats on resource usage, but exclude it, at the node level, from alerting.
