Composite Domain: no values visible in "Value Relations"?

Answered Composite Domain: no values visible in "Value Relations"?

  • Monday, February 06, 2012 10:07 PM
     
     

    Hi,

    I am setting up an environment with DQS (SS2012 RC0) and am playing around with composite domains. This is what I did:

    • Created new KB.
    • Created single domain "Street"
    • Created single domain "Number"
    • Created composite domain "StreetNumber" consiting of the single domains "Street" and "Number".
    • Imported a text file and mapped this to the composite domain having the following contents:

      Street;Number
      NameA;NumberA
      NameB;NumberB

    The import executes as expected:

    • NameA and NameB are loaded into the single domain Street.
    • NumberA and NumberB are loaded into the single domain Number.

    But, why do I NOT see any values in the composite domain "Value Relations"? I expected there a table with two records "NameA | NumberA" and "NameB | NumberB"?

    Is this a bug in the current release, and how can this be fixed?

    Regards,

    Johan Machielse

All Replies

  • Tuesday, February 07, 2012 6:58 PM
    Moderator
     
     Answered

    If I remember correctly, Value Relations tab only shows value pairings where the frequency is 20 or higher occurances of that pair.

    I asked around to see if there is any configuration knob to change this threshold, and we didn't find one.

    I think it is a good design change request to see all value relations, so please post it at http://connect.microsoft.com under the SQL Server project there.

    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

  • Friday, November 23, 2012 1:50 PM
     
      Has Code

    If you query the DQS DB, the Knowledge Discovery definitely seems to be adding the Value Relations regardless of whether they are showing up in the UI.  Has anyone done any testing to validate that the cleansing rules will use the Value Relations even though the frequency is low (1)?

    USE [DQS_MAIN]
    SELECT 
    COMPOSITE.ID, COMPOSITE.FREQUENCY, 
    CITY.ALGORITHM_VALUE AS CITY, 
    STATE.ALGORITHM_VALUE AS STATE, 
    COUNTRY.ALGORITHM_VALUE AS COUNTRY 
    FROM
    [KnowledgeBase1000001].[B_COMPOSITE_DOMAIN_VALUE_RELATION] COMPOSITE
    INNER JOIN 
    	(SELECT Value.ID, Value.ALGORITHM_VALUE, Field.NAME 
    	 FROM [KnowledgeBase1000001].[B_INDEX_LEXICON] Value INNER JOIN [KnowledgeBase1000001].[B_DATA_SERVICE_FIELD] Field ON Value.LEXICON_FIELD_ID = Field.ID) CITY 
    	 ON COMPOSITE.FIELD_1 = CITY.ID
    INNER JOIN 
    	(SELECT Value.ID, Value.ALGORITHM_VALUE, Field.NAME 
    	 FROM [KnowledgeBase1000001].[B_INDEX_LEXICON] Value INNER JOIN [KnowledgeBase1000001].[B_DATA_SERVICE_FIELD] Field ON Value.LEXICON_FIELD_ID = Field.ID) STATE
    	 ON COMPOSITE.FIELD_2 = STATE.ID
    INNER JOIN 
    	(SELECT Value.ID, Value.ALGORITHM_VALUE, Field.NAME 
    	 FROM [KnowledgeBase1000001].[B_INDEX_LEXICON] Value INNER JOIN [KnowledgeBase1000001].[B_DATA_SERVICE_FIELD] Field ON Value.LEXICON_FIELD_ID = Field.ID) COUNTRY
    	 ON COMPOSITE.FIELD_3 = COUNTRY.ID
    WHERE
    	COMPOSITE_DOMAIN_ID = 1003--(SELECT ID FROM [KnowledgeBase1000001].[B_DATA_SERVICE_FIELD] WHERE NAME = 'CityStateCountry')