Wednesday, 10 January 2018

SCOM: SQL Instance and Databases exclusion

This  post is by Chris Gibson

I recently wanted to exclude some temporary SQL databases from being discovered by our SCOM environment.  These databases are created during a backup process and are always named _Clone”.  I’d previously excluded SQL Express instances by their name (Maps, Live, MSEE) and it worked a treat.  However, this was done by their full name and not a partial name using a wildcard.

If you take the SQL 2014 discovery for databases, (MSSQL 2014: Discover Databases for a Database Engine), for examples and override it.  You will see “you can use the wildcard * to exclude all databases” in the details pane.  Why this would be included when you could just disable the discovery all together I’m not sure, but it seems almost criminal that you can’t disable discovery of databases or instances (the discoveries have the same options as this one) via a partial name.  Something like “*_Clone” or "%_Clone" which would solve my problem and i’m sure its something other people would find useful?

So, rather than just ranting I have raised a user voice request to get this functionality changed.  Microsoft takes notice of these suggestions and if popular enough and technically possible, they can make there way into the next release of a product (or an MP in this case).  So please take a moment to check out the below link and give it the full 3 votes



https://systemcenterom.uservoice.com/forums/293064-general-operations-manager-feedback/suggestions/32838001-allow-wildcards-to-exclude-some-databases-instance



1 comment:

  1. Try it again but removing the underscore character e.g. %Clone in SCOM the _ is often used as a place holder character. Not sure if this will help but try it to see.

    Ernie

    ReplyDelete

Featured post

Creating a Linked Server to an Azure SQL Database

Why would you create a Linked Server to an Azure SQL Database? If you work in a hybrid environment with some databases stored on your on ...