Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
9Activity
0 of .
Results for:
No results containing your search query
P. 1
Star Scema

Star Scema

Ratings: (0)|Views: 353 |Likes:
Published by api-26355935

More info:

Published by: api-26355935 on Oct 15, 2008
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PPT, PDF, TXT or read online from Scribd
See more
See less

03/18/2014

pdf

text

original

Sudarshan
Copyright \u00a9 1995-1996 Archer Decision Sciences, Inc.
The \u201cC la ssic \u201d Sta r Sc hemaPERIO D KEY
Store Dimension
Time Dimension
Produc t Dimension
STO RE KEY
PRO DUC T KEY
PERIO D KEY
Dollars
Units
Pric e
Period Desc
Year
Quarter
Month
Day
Fact Table
PRO DUC T KEY
Store Desc ription
C ity
Sta te
Distric t ID
Distric t Desc .
Region_ID
Region Desc .
Regional Mgr.
Produc t Desc .
Bra nd
Color
Size
Manufac turer
STORE KEY
Sudarshan
Copyright \u00a9 1995-1996 Archer Decision Sciences, Inc.
The \u201cClassic\u201d Star Schema
\ue000A single fact table, with
detail and summary data
\ue000Fact table primary key has
only one key column per
dimension
\ue000Each key is generated
\ue000Each dimension is a single
table, highly denormalized
Benefits: Easy to understand, easy to define hierarchies, reduces # of physical joins, low
maintenance, very simple metadata
Drawbacks:Summary data in the fact table yields poorer performance for summary
levels, huge dimension tables a problem
PERIO D KEY
Store Dimension
Time Dimension
Produc t Dimension
STO RE KEY
PRO DUC T KEY
PERIO D KEY
Dollars
Units
Pric e
Period Desc
Year
Quarter
Month
Day
Current Flag
Resolution
Sequence
Fact Table
PRO DUC T KEY
Store Desc ription
C ity
Sta te
Distric t ID
Distric t De sc .
Region_ID
Region Desc .
Regional Mgr.
Level
Produc t Desc .
Bra nd
C olor
Size
Ma nufa c turer
Level
STORE KEY
The \u201cClassic\u201d Star Schema
Sudarshan
The biggest drawback:dimension

tables must carry a \u201clevel\u201d
indicator for every record and
every query must use it. In the
example below, without the level
constraint, keys for all stores in the
NORTH region, including
aggregates for region and district
will be pulled from the fact table,
resulting in error.

Example: Select A.STORE_KEY, A.PERIOD_KEY, A.dollars
from Fact_Table A

where A.STORE_KEY in (select STORE_KEY
from Store_Dimension B
where region = \u201cNorth\u201d and Level = 2)

and etc...

Level is needed
whenever aggregates
are stored with detail
facts.

PERIO D KEY
Store Dimension
Time Dimension
Produc t Dimension
STO RE KEY
PRO DUC T KEY
PERIO D KEY
Dollars
Units
Pric e
Period Desc
Year
Quarter
Month
Da y
Current Flag
Resolution
Sequence
Fact Table
PRO DUC T KEY
Store Desc ription
C ity
Sta te
Distric t ID
Distric t Desc .
Region_ID
Region Desc .
Regional Mgr.
Level
Produc t Desc .
Bra nd
Color
Size
Ma nufa c turer
Level
STORE KEY

Activity (9)

You've already reviewed this. Edit your review.
1 thousand reads
1 hundred reads
munishiiii liked this
Honey Singla liked this
13sims liked this
faridsk liked this
badutzz liked this
Ajay Joshi liked this

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->