RE: Newbie design question

Hi Ed,
I recommend that you create two dimensions here, one for Consultant, one
for Customer, though currently they are one to one. Flexibly considering
one day for some special cases, you need to assign two or more consultants
to your customer. In this case, you need not do anything if you have
separated them to two dimensions.

I would like to recommend two books for you:
Mastering Data Warehouse Design: Relational and Dimensional Techniques
http://www.amazon.com/Mastering-Data-Warehouse-Design-Dimensional/dp/0471324
213
Data Warehouse Design Solutions
http://www.amazon.com/Warehouse-Design-Solutions-Christopher-Adamson/dp/0471
25195X

Hope this helps. Please feel free to let me know if you have any other
questions or concerns.

Best regards,
Charles Wang
Microsoft Online Community Support

======================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================



.

Relevant Pages

  • Re: Sums along dimension - Pls help!
    ... I have 4 dimensions. ... Brochures ... * Parent Group Name Ex: Bunnings Victoria ... * Customer Account Name Ex: ...
    (microsoft.public.sqlserver.olap)
  • Re: A bit confused about "changing" dimensions.
    ... Managers, and I believe that in a changing dimension the lowest level isn't ... > customer changes from 1 group to another. ... we have two types of dimensions: ... >> history). ...
    (microsoft.public.sqlserver.olap)
  • Re: Advice needed for large dimension
    ... hierachy out of this made ... Besides this there is some litterature about VLDM - very large dimensions - ... > Store Customer ProductGrp Period1 Period2 Change ...
    (microsoft.public.sqlserver.olap)
  • Autoexist
    ... Each customer can have a different segment for each product. ... snowflake schemas do not support this type of relationship we just ... an alternative way in AS 2000) through many-to-many dimensions. ...
    (microsoft.public.sqlserver.olap)
  • Re: 800 Dimensions... Too many?
    ... using separated tables for the dimensions is a first step. ... this reduce the size of the cube and provides a better process performance. ... I would recommend building the dimensions from real dimension ... Please do not send email directly to this alias. ...
    (microsoft.public.sqlserver.olap)
Loading