Sign in
 
Home20122008 R2200820052000LibraryForums
SQL Server >
> 
> 
Using a Master Data Services entity view as reference data set for a DQS domain

Answered Using a Master Data Services entity view as reference data set for a DQS domain

  • Friday, May 11, 2012 2:03 PM
     
     
    Sign In to Vote
    0

    Hi,

    Many of my customers domains are of no public interest and will never be found on the Azure marketplace, but will be hosted in Master Data Services instances within the enterprises. So in order to create master data processes / data quality processes that make sense to the customers I therefore need to connect the DQS domains to "internal" reference data sets that would be MDS entity export views.

    Is this a functionality that we can expect in DQS?

    Best regards Magnus W.

    Magnus Wernersson


     

All Replies

  • Sunday, May 13, 2012 1:30 PM
    Moderator
     
     
    Sign In to Vote
    0

    You can make a MDS subscription view to publish or "export" your data values for consumption elsewhere.

    http://sqlblog.com/blogs/mds_team/archive/2010/03/03/publishing-master-data-with-subscription-views-part-1-the-basics.aspx

    If your MDS values are already in the clean and perfect state, Next do DQS Discovery knowledge management activity to "import" the MDS entity, for each required column add a matching domain, and discovery will consume the values as initial knowledge, or make a fresh design and on each domain Import a column at a time.

    http://technet.microsoft.com/en-us/library/hh510398.aspx

    Video http://msdn.microsoft.com/en-us/sqlserver/hh323825.aspx

    In my opinion, the experience is not seemless as a subscription between the two functional areas, because it doesn't autorefresh the Kb with new MDS values, but I think the product group is aware and will take note for the future releases.

    Hope that is a push in the right direction. Thanks, Jason

    Didn't get enough help here? Submit a case with the Microsoft Customer Support team for deeper investigation - http://support.microsoft.com/select/default.aspx?target=assistance

     
  • Sunday, May 13, 2012 9:48 PM
     
     
    Sign In to Vote
    0

    Hi,

    Yes OK. But that means we need to put somebody to physically run the process, what needs to be done is instead a much higher grade of automation, which could be achieved if we, ourselves, could define a view to be used as a reference data set to a DQS domain. Right now this is actually a showstopper that prevents us from going all in and recommend a SQL Server based MDM / DQ solution for customers in the international/premium/fortune segments using MDS / DQS.

    How is the roadmap forward looking? Is this something that'll happen in an upcoming CU?

    Because if we know today that this will be possible in a near future, we can still recommend the suite and do all the other work that needs to done meanwhile.

    Best regards Magnus W.

    Magnus Wernersson

     
  • Monday, May 14, 2012 2:43 AM
    Moderator
     
     
    Sign In to Vote
    0

    Sorry that it is what it is. SQL generally doesn't add any features in cumulative updates, those patches are for urgent bug fixes.

    Its good feedback to hear, but you won't reach the product group here. Please file the idea on Connect.Microsoft.com

    I can forward this public thread to the decision makers as well.

    Thanks, Jason

    Didn't get enough help here? Submit a case with the Microsoft Customer Support team for deeper investigation - http://support.microsoft.com/select/default.aspx?target=assistance

     
  • Monday, May 14, 2012 4:50 AM
     
     Answered
    Sign In to Vote
    0

    Our roadmap includes alignment of MDS entities and business rules with DQS domains. The top request we've heard from customers so far is to enable use of 'list of known good values' from a DQS domain as an MDS 'domain based attribute' and we're going to frontload this work for the next offering. The opposite scenario that I believe you are refering to is interesting as well (I assume that the domains are hosted in MDS for governance purposes?), though the DQS domain usually contains much more than known good values (known errors, rules, TBRs...). Some are possible (like DQS rules from MDS business rules) but will require more work/time. 

    We do plan in the nearest future to provide reuse of RDSs across knowledgebases within the enterprise (via an Enterprise DataHub) as well (in addition to the marketplace).

     
  • Monday, May 14, 2012 6:59 AM
     
     
    Sign In to Vote
    0

    Hi,

    OK, thank you. That'll solve my concerns around the MDM / DQ processes. Even if I may sound a little bit frustrated above I'm really fond of the MDS / DQS products. They're filling a data management gap, that we partners now with confidence can offer our customers.

    Best regards Magnus W.

    Magnus Wernersson