Create Dynamic Instance Group


  • Hi All,

    I am wondering if this is possible, I would like to create a dynamic group populated with only Read Only SQL Databases and their respective servers. Logic being I want to override certain rules/monitors and not have them run on machines that SCOM only has RO access to the DB's. Your help is greatly apreciated.



    Friday, February 10, 2012 8:10 PM


All replies

  • Hi,

    To create dynamic group, please refer to the following example:

    Operations Manager Dynamic Group Examples

    I think you can try the properties in the Query Builder to create the group. If this could not meet your requirements, please also see the following method:

    Populating groups from a SQL server CMDB – step by step

    To determine if the database is read-only, I think you try the following:


    Hope this helps.


    Nicholas Li

    TechNet Community Support

    Tuesday, February 14, 2012 7:01 AM
  • Thank you Nicholas,

    Do you think there is a possibility of this working?

    Create Dynamic group "( Object is SQL Database AND ( Updateability Equals READ_ONLY ) AND True )" then override this discovery "Discover Databases for a

    Database Engine" for a group, being the newly created dynamic group populated with READ_ONLY databases. Does the new group need to be sealed?



    Wednesday, February 15, 2012 6:37 PM
  • Hi Matt

    Does the new group need to be sealed?

    The management pack that the group is created in does not need to be sealed if you are only creating overrides against the rules \ monitors \ discoveries that are provided in the sealed Microsoft Management Packs.

    If you are creating your own rules \ monitors \ discoveries then you can create the group in the same management pack as the base rule \ monitor \ discovery and not worry about sealing the management pack.

    The basic requirement is that you can't reference an unsealed management pack from another unsealed management pack.

    Then override this discovery "Discover Databases for a Database Engine" for a group ..

    I don't have a system to test this on to hand but my thoughts are that this specific example won't work. Your group is a group of databases - you check to see if this part of the process works by right clicking the group and View Members to see if the correct databases are listed. You could then use this to override rules \ monitors targetted at the SQL database class. But not at the SQL DB Engine class.

    Discover databases discovery is targeted at SQL DB Engine so it won't work for this. There is an exclude list on the Discover Databases discovery which you can fill in manually (but it won't accept a group or any form of automation).



    New SCOM 2012 Blog! -
    View OpsMgr tips and tricks at

    Friday, February 17, 2012 12:57 PM