Comments on:

By: mark blakey

Tue, 07 Feb 2012 10:24:57 GMT

Thanks, have been looking for something like this

By: Joe Mead

Fri, 13 Jan 2012 18:42:33 GMT

Found our issue. The account used for SQL needed to be distributed to the RMS. It does not go there by default if there is no SQL Server on the RMS.

By: Joe Mead

Thu, 12 Jan 2012 16:03:47 GMT

Not us. The console views are not populating.

By: Al Howarth

Thu, 05 Jan 2012 20:02:12 GMT

Does anyone have this working?

Has anyone been able to receive support from the developer?

By: mrgangster

Mon, 28 Nov 2011 13:53:32 GMT

how can i enable SQL Server Desired DB Mirroring Configuration Discovery? I need monitor when mirror change state from Master to Mirror state. I have read instruction and made DesiredDBMirrors.xml and put in on RMS Server C: location, but when mirror change state I have no alert. Please help

By: GG

Fri, 21 Oct 2011 00:26:28 GMT

I am having a problem with the "Desired Configuration" in regards to the monitor Database Mirror Role Compliance. In the Health Explorer, I keep seeing the Role in a warning state. Furthemore, the alert shows the following:

Database mirror not currently running according to its desired configuration.
Database Name:
Desired Principal: / Current Principal:
Desired Mirror: / Current Mirror:

I have verified my servers and they are correct. The desired server in the XML does indeed match what is actually in place.

The alert description has the following in it (note the "desired" and "actual" both pull a variable named "Desired..."):

Desired Principal: $Target/Property[Type="MirroringLibrary!RABurri.SQLServer.Mirroring.ComponentGroup"]/DesiredMasterComputerPrincipalName$ / Current Principal: $Target/Property[Type="MirroringLibrary!RABurri.SQLServer.Mirroring.ComponentGroup"]/DesiredMirrorComputerPrincipalName$

Desired Mirror: $Target/Property[Type="MirroringLibrary!RABurri.SQLServer.Mirroring.ComponentGroup"]/DesiredMirrorComputerPrincipalName$ / Current Mirror: $Target/Property[Type="MirroringLibrary!RABurri.SQLServer.Mirroring.ComponentGroup"]/DesiredMasterComputerPrincipalName$

Since it seems these always pull out of the XML and pulling opposite servers it appears it is attempting to resolve

Principal = Mirror

which will always resolve to false.

Anyone else seen this behavior?

Thank you,
Gary
DBA

By: Raphael Burri

Fri, 10 Sep 2010 13:15:21 GMT

I have just published the update to version 1.0.1.72 which adds support for SQL Server 2005.

By: user not found

Mon, 12 Jul 2010 18:29:36 GMT

By: Stefan Koell

Fri, 04 Jun 2010 15:06:58 GMT

looks very promising, Raphael!