MDS Business Rules vs DQS Domain Rules RRS feed

  • Question

  • Some MDS rule operators and actions overlap DQS domain rules.  When deciding where to place the rules for validating data, is there a best practice on where to place the rules?

    Javier Guillen

    Tuesday, July 31, 2012 6:37 PM


  • Hello Javier,

    You might find the following white paper useful: Cleanse and Match Master Data by Using EIM.

    There is a section in this white paper that talks about DQS and MDS rules. I am copying the content from the white paper below:

    Master Data Services business rules and Data Quality Services domain rules

    Business rules in Master Data Services and domain rules in Data Quality Services are both used to maintain the integrity of data, but they are used in different circumstances, as part of different operations, and from within different tools. Domain rules are used to identify data problems as part of a cleansing project, while business rules are used to prevent bad data from being introduced into Master Data Services. The two types of rules can apply to the same data at different places in the information management lifecycle, so the same rule can end up being defined in both places.

    Domain Rules

    A domain rule is used in the cleansing processes performed in Data Quality Services to identify problematic records. Domain rules are established in the domain management performed in the Data Quality client, and they are included in the applicable knowledge base.

    A domain rule enables you to specify conditions for the data that you are cleansing. You can add rules to specify values that are not allowed, and what the available values are or what the range of values is. Each record you cleanse is validated against the rules that apply to the domains in the record. If a check of a value fails, the value is marked as invalid.

    Business Rules

    A business rule is used in Master Data Services to prevent the entry of problematic records. Business rules are created within the Master Data Manager Explorer, and they are part of the master data model.

    A business rule prevents the improper entry or modification of records. It is not about identifying master data within an entity that is already incorrect. It's about keeping bad data from being added to the MDM or introduced within the MDM. Master Data Services will prevent you from entering a new record or modifying an existing value if doing so would violate a business rule. Multiple processes trigger this validation of master data. Whenever you add or change data into the MDM, whether it's through the Excel Add-in, entity-based staging, the Web UI, or the API, applicable business rules are run on the records that are added or changed. If you are manually making changes in the MDM, you can use a business rule to validate the changes.

    Hope its useful for you.

    SQL Server Documentation

    Friday, November 2, 2012 9:12 PM