Design domains

Question

Hi,

I search in the forum but don't find a question related, so here I am.

Are there some best practices to design the domains in a KB? I understand the domains as fields of a table (more or less), but don't know if this is a good aproximation or I have to think in a different way.

Thanks in advance.

Answer 1

Looking at domains as they were columns in a table is a good approach, but there are exceptions.
For example, an address domain can consist of multiple columns in a table (street - housenumber - zipcode - city - ...). Full name can consist of prefix - first name - middle name - last name - suffix. You can capture this using the composite domains in DQS.

But since the source for DQS is relational - Excel or SQL Server - the comparison with columns pretty much always goes up.

Best practices? Not every domain needs to store all possible values. Just a rule can be enough. For example, an emailaddress domain that checks if the emailaddress is valid only needs a regular expression. It would be quite silly to try to store every possible emailaddress.

---

MCTS, MCITP - Please mark posts as answered where appropriate.

Answer 2

Thanks Koen.

Ok, so I'll do this.