SQL Server Developer Center > SQL Server Forums > SQL Server Data Quality Services > Can you create domains automatically from Source columns?

Answered Can you create domains automatically from Source columns?

  • Friday, July 29, 2011 4:55 AM
     
     

    Not sure if I'm missing something, but when creating a new KB in Knowledge Discovery Mode, it appears you have to manually create and map new domains for each column.

    I'd expect on a 1st pass to be able to autocreate domains based on the column metadata....

    Actually, add to this, the client interpets Excel fields as string... so if they contain numeric data you cannot map them to a Numeric domain.

    How / where can we report bugs? Do you have Connect up for this yet?

    Cheers, James


    James Beresford @ www.bimonkey.com
    SSIS / MSBI Consultant in Sydney, Australia
    SSIS ETL Execution Control and Management Framework @ SSIS ETL Framework on Codeplex
    • Changed Type BI Monkey Wednesday, August 03, 2011 1:09 AM
    •  

Answers

  • Friday, July 29, 2011 8:53 PM
    Moderator
     
     Answered

    Hi,

    Connect is already set up for this, feel free to report bugs, issues and recommendations through the Connect site.

    As for discovery - yes, at this stage, you have to manually create and map the domains - we do not automatically publish the KB with any data. The thinking was that in many cases out of 50 columns in your source, you are only really interested in learning / discovering knowledge about 3 or 4, so auto-population of all columns into the KB does not make sense.

    We will look into providing some better support for this use case - I Will update you with any progress.

    As for Excel - this is a known issue in CTP3 that we have already fixed in the next update. As a workaround, you can import the column values from Excel directly into the domain (from the value management window), and not run them through discovery.

    Hope this helps.

    Thanks,

    Elad

    • Marked As Answer by BI Monkey Wednesday, August 03, 2011 1:09 AM
    •  

All Replies

  • Friday, July 29, 2011 8:53 PM
    Moderator
     
     Answered

    Hi,

    Connect is already set up for this, feel free to report bugs, issues and recommendations through the Connect site.

    As for discovery - yes, at this stage, you have to manually create and map the domains - we do not automatically publish the KB with any data. The thinking was that in many cases out of 50 columns in your source, you are only really interested in learning / discovering knowledge about 3 or 4, so auto-population of all columns into the KB does not make sense.

    We will look into providing some better support for this use case - I Will update you with any progress.

    As for Excel - this is a known issue in CTP3 that we have already fixed in the next update. As a workaround, you can import the column values from Excel directly into the domain (from the value management window), and not run them through discovery.

    Hope this helps.

    Thanks,

    Elad

    • Marked As Answer by BI Monkey Wednesday, August 03, 2011 1:09 AM
    •  
  • Saturday, July 30, 2011 7:15 AM
     
     

    Hi

     

    RE: columns, I wasn't thinking of auto-mapping all domains - more a case of if you select a column, you should have an option to generate a domain from that columns metadata. Of particular value first time you build a KB, as manually creating domains would get tedious pretty quickly in a big project.

     

    Cheers, James


    James Beresford @ www.bimonkey.com
    SSIS / MSBI Consultant in Sydney, Australia
    SSIS ETL Execution Control and Management Framework @ SSIS ETL Framework on Codeplex