Stop monitoring SQL Express and Windows Internal Database

re: Stop monitoring SQL Express and Windows Internal Database

Gibson26 — Tue, 11 Jun 2013 12:23:56 GMT

Hi Kevin,

I've followed the steps you described above to the letter, but it seems I cannot get the same result.

Not a single SQLEXPRESS is undiscovered; they still appear in the discovered inventory (even after 24+ hour). The discovery is set for 4 hours.

In your override screenshot i noticed the Enabled property set to False (grey), so i assume you've set it in another override?

Is that what I'm missing, or shouldn't it be of any influence?

Thx,

Dennis

re: Stop monitoring SQL Express and Windows Internal Database

Per J — Tue, 05 Mar 2013 08:33:02 GMT

Hi,

I'm experiencing the same as Nicole, I've added a number of instances to exclude, but my already discovered instances are still there. The only way I've been able to make them disappear, were by re-installing the agent.

My theory is that the DB engine is no longer directly discovered with the Windows Server as target, rather than SQL Server installation seed. Even after making the server disappear from that discovery the SQL instances still hang around.

I'm doing some more tests, and will hopefully find an easy workaround.

/Per

re: Stop monitoring SQL Express and Windows Internal Database

Nicole Welch — Thu, 01 Nov 2012 19:42:21 GMT

Kevin - thanks for the quick reply! I removed the instance with the $ and confirmed my SQL2005/2008 exceptions match. Unfortuantely, no errors are generated and Express instances still appear. I've even reset the health store and restarted a few agents. I've also tried shortening my exclusion list - in case there is a max field size -- but there's no change. Any other thoughts?

re: Stop monitoring SQL Express and Windows Internal Database

Kevin Holman — Thu, 01 Nov 2012 17:42:22 GMT

Oh - and Nicole - feel free to ping me directly in email anytime.

re: Stop monitoring SQL Express and Windows Internal Database

Kevin Holman — Thu, 01 Nov 2012 17:41:30 GMT

First - when using the parameter override for discovery "ExcludeList", running Remove-DisabledMonitoringObject will not do anything. This is by design. When we are using ExcludeList - we need the discovery to run, and to UNDISCOVER the SQL instance by name. So we must ensure that the discovery is not "disabled" on the host server.

Your list looks good. However - you might need to ensure you are putting these same exclusions in on your SQL server 2008 discovery rule as well.

Additionally - one thing to point out - some workflows don't handle any test with a "$" in there - because it thinks it is a variable. You might consider removing the one with the $ signs and see if that fixes it. Also - if you have overridden the frequency of the SQL DB engine discovery in the past - you might want to consider changing that back for the purposes of testing your changes. Or just restarting the agent to force it to run all discoveries at startup.

re: Stop monitoring SQL Express and Windows Internal Database

Nicole Welch — Thu, 01 Nov 2012 13:56:13 GMT

So when I do this only ~10% disappear. I've waited 24hr and run remove-disabledmonitoringobject as well (multiple times). I'm running SCOM 2007 R2 infra, SCOM 2012 agents, SQL MP 6.3.173.1. Targeting overrides to Windows Server and the SQL Discovery Seed actually excluded more than just targeting Windows server. Below is one of my overrides - pls tell me I've just made a simple mistake!

ID="OverrideForDiscoveryMicrosoftSQLServer2005DBEngineDiscoveryRuleServerForContextMicrosoftWindowsServerComputer44870d24b20d485f9c96ae9f74ceaf45" Context="Windows!Microsoft.Windows.Server.Computer" Enforced="false" Discovery="SQLServer!Microsoft.SQLServer.2005.DBEngineDiscoveryRule.Server" Parameter="ExcludeList" Module="DS">

<Value>ECSQLEXPRESS,MICROSOFT##SSEE,SQLEXPRESS,SQLEXPRESS1,SQLEXPRESSTEST,AUTODESKVAULT,BKUPEXEC,QUADRATE,BPASERVER8,SQLExpress,HPWJA,MICROSOFT$VMM$,VIM_SQLEXP,WINTOOL</Value>

re: Stop monitoring SQL Express and Windows Internal Database

Kevin Holman — Thu, 14 Jun 2012 21:21:42 GMT

@vijayh -

You can a few options. Uninstall SQL express. Or - create an override to disable discovery of the Express instance BY NAME - as posted above - ONLY for this specific server. Then any other SQL instance will be discovered.

re: Stop monitoring SQL Express and Windows Internal Database

vijayh — Wed, 13 Jun 2012 11:35:10 GMT

Hello Kevin, 13 Jun 2012 4:32 AM

I've few sqlexpress edition with instance name as MSSQLSERVER, i created one group based on windows computer and override in the discovery to enable as False for this group. But now DBA team installed standard edition in the same server,now the server has both express edition and standard edition. it is not discovered due to disable the discovery, now i want to discover that standard edition instance but SQLEXPRESS should not be discovered.

How can i achieve this?

re: Stop monitoring SQL Express and Windows Internal Database

Hello Kevin, — Wed, 13 Jun 2012 11:32:40 GMT

How can i achieve this?

re: Stop monitoring SQL Express and Windows Internal Database

Kevin Holman — Tue, 07 Sep 2010 13:01:51 GMT

I looked - the discoveries are identical.... The only thing that changed is displayname, and the script for the datasource. I cannot imagine why these would populate again if your override was in place.