Mirroring monitoring issues - by Azhar Taj

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 266658 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 3/30/2007 3:19:26 PM
Access Restriction Public


Yukon Mirroring Monitoring DCR’s:

1.	We should be able to specify the mirroring event type logged in the Event Viewer, e.g., we should be able to specify in the configuration that for mirroring Performance Alerts, e.g., “Warn if the unsent log exceeds the threshold > 150 MB”, log an event of type “error” in the Event Viewer. These mirroring performance alerts should be visible under SqlServerAgent  Alerts. At this time, they are only visible in the Mirroring Monitor GUI.
2.	We should be able to configure as to how frequently data is written to the tables by the mirroring monitor GUI. The current setting is every 30 seconds. This generates alerts every 30 seconds, which is excessive in a support environment.
3.	For mirroring performance alerts, database name should be part of the alert.
4.	For WMI mirroring state change alerts, server name and db name should be part of the alerts.
5.	For WMI state change alerts, at this time we need to create new alerts every time mirroring is added for a new database and then delete the same when mirroring is removed for a particular database. This is very cumbersome in a support environment. We would rather have one alert per dbm state that would fire for all databases and have the event notification which contains both the server and database names (which are both possible as there are member variables in the Datablock structure to hold these values). Also, those WMI mirroring state change alerts should be created by default (visible under SqlServerAgent  Alerts), when we install mirroring. We should not have to manually run scripts to create them.
Sign in to post a comment.
Posted by Microsoft on 9/12/2012 at 8:37 AM
This is to inform that this change request is closed as won't fix as a part resolving DCRs which have not been addressed in multiple release cycles. If this decision has a high business impact on your use scenario, please inform us with SQL Server version.

Best Regards,
Posted by Microsoft on 5/3/2007 at 11:07 AM
Thank you for your detailed feedback, it is very useful.

We will go through each of your suggestions and try to address them in a future release.