I came across an environment where there were multiple SharePoint environments.  These SharePoint environments were split into Test and Production, and held Configuration Databases on a separate Database Instance, per Best Practice. In order to tune the DB Connection you need to tune the Alert by creating Overrides for each environment.  I outline this process below:


If you have more than one DB Instance holding Configuration Databases, you will need to create an OpsMgr group and add the DB Instance or DB Server to the OpsMgr group.  This will be used later on for the Override.
1.      Create an Override Groups MP
2.      Create two new Groups, then save them into the Override Groups MP you created
o   Test SharePoint Configuration Database Group

o   Production SharePoint Configuration Database Group

Go to Monitoring\Configuration Databases


Open Health Explorer and Highlight SQL Database Connection Failed


Go to Overrides (Top Right), and Override the Monitor for:

·        If there is more than one DB Instance (test or production) environment, override ‘For a Group’

o   This is the group you created in the initial steps

·        If there is just one DB Instance, override ‘For all Objects of class: SharePoint Configuration Database’


Click the Override check box to change the default ConnectionString:

·        Provider=SQLOLEDB;$Target/Property[Type="Microsoft.SharePoint.Foundation.2010.SPDatabase"]/ConnectionString$


Change the Connection String Override value to the following value:

Note: Change “SP2010DBInstance” to your DB Instance Name

·        Provider=SQLOLEDB;Data Source=SP2010DBInstance;Initial Catalog=SharePoint_AdminContent_83b59406-871e-4937-892e-242ff2ea17e3;Integrated Security=SSPI;Enlist=False;Connect Timeout=15

You can change the IntervalSeconds value to initiate the ConnectionString after 2 minutes in order to see if the changes made works quickly:

Note: The effective value is False, this should be changed to True

1.      Click the Override checkbox for ‘Enabled’

2.      Drop the Override Value down to False

3.      Click apply

4.      Drop the Override Value down to True

5.      Click OK

Note: You will see the exclamation next to the override stating that you cannot change the value to True. This means you need to change the Override Value to False, then back to True (somewhat confusing)


The destination management pack to save the override in automatically defaults to the Overrides Group MP you created above.

Click OK, and wait a few minutes to see if your changes made to the ConnectionString value worked.

If it did work, then backout the Interval seconds value change so you don’t run the ConnectionString so frequently now that you know it worked:

        Open up the Health Explorer as in previous steps

If this is OpsMgr 2012, click the X next to Scope is only unhealthy child monitors so you can see all Health Monitors


Expand Availability under Entity Health


Highlight SQL Database Connection Failed, then go to Overrides and change ‘per object’ or ‘all objects of class’, depending on if this is a single DB Instance or split for Test and Production reasons, noted in a previous step:


Remove the Override checkbox for IntervalSeconds then click OK:


Configuration Database State View should show Healthy: