because generally its easy to maintain in most cases.
If you have 1 table with a clean list of customers, its easier to create a
dimension based on this table and use another table for the fact table (the
sales information)
also, if you look at the queries launched by AS, you'll see that AS run
Select DISTINCT statements to fill its dimensions, because each customer
appear only 1 time in a dimension, if you fact table has 1 000 000 rows for
only 100 customers, the distinct command takes a very long time.
also, if the name of the customer is 50 characters * 1 000 000 = 50 000
000bytes huge table !!! but a customer key which is an INTEGER type takes 4
bytes * 1 000 000 = 4 000 000bytes
also, if want to share the same dimension on 2 different cubes, AS will
create inner join between your dimension table and your fact table (except
in specific cases not describe here), so an inner join between 2 tables with
1 millions of row each is very long!
its why a star schema is recommended.
but if your cube is based on a small table, then, there is no problems.
I hope this can help you.
Jerome.
"Rico Cali" <ricocali (AT) hotmail (DOT) com> a écrit dans le message de news:
675e1895.0409060902.5f19e18a (AT) po...OT) google.com...
Quote:
Thank you Jeje, but why does MS recommend a star/snow-flake schema for
data-source? Is it because it's faster to read? |