DRAG DROP
You are loading a dataset into SQL Server. The dataset contains numerous duplicates for
the Artist and Song columns.
The values in the Artist column in the dataset must exactly match the values in the Artist
domain in the knowledge base. The values in the Song column in the dataset can be a close
match with the values in the Song domain.
You need to use SQL Server Data Quality Services (DQS) to define a matching policy rule to
identify duplicates.
How should you configure the Rule Editor? (To answer, drag the appropriate answers to the
answer area.)
Answer: 
If ‘the values in the Song column in the dataset can be a close match with the values in the Song domain’, why then can’t the WEIGHT be “50” for song and “50” for Artist?! At least, the sum of all weighted scores still wouldn’t have exceeded 100!!
Again, if ‘the Artist column in the dataset must exactly match the values in the Artist
domain in the KB’, would it be enough for obtaining an exact match w/out giving it any ‘score for weight’ while just indicating YES for Prerequisite?!
0
0
No one uses this tool, that’s why its such a mystery
Since artist is an exact match, prerequisite is a yes. Setting prerequisite to yes is the same as setting exact match and overrides the fact that similarity is set to similar in this example. It’s really exact.
So, weight must be 100 with song because weight must sum to 100 and artist is ascribed no weight since its a prerequisite. If the prerequisite is not met, it doesn’t matter what the weight is, it will fail, so weight is grayed out if prerequisite is set to yes
prerequisite for song is no because it only has to be similar. Unclear where to set similar, but you can check here
https://blogs.msdn.microsoft.com/dqs/2011/11/02/matching-policy-a-closer-look-into-data-quality-services-data-matching/
1
0
Henry thank you for your detailed explanation 🙂
2
0