Welcome to the dBforums forums.

You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!

If you have any problems with the registration process or your account login, please contact contact support.

If you prefer not to see double-underlined words and corresponding ads, place your cursor
here for ContentLink opt out.

Go Back  dBforums > General > Database Concepts & Design > star model: references between two fact tables?

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 06-24-03, 07:11
ort_pf ort_pf is offline
Registered User
 
Join Date: Jun 2003
Posts: 4
Post star model: references between two fact tables?

Hi!

I am designing a data warehouse model in which it seems we would need multiple fact tables. According to what I've read, multiple fact tables doesn't interfere with the theory of the star model. However, it seems that some of the fact tables must "use" other fact tables as dimension tables.

Is that allowed in the star model?
Is it ok anyway, or is it poor design?

I also would like to get useful links to Data Warehouse Design pages on the net. The best I have now is "Data Warehouse Design considerations" on MSDN.

Thanks in advance,
Peter
Reply With Quote
  #2 (permalink)  
Old 06-24-03, 08:13
r937 r937 is offline
SQL Consultant
 
Join Date: Apr 2002
Location: Toronto, Canada
Posts: 13,558
Quote:
The best I have now is "Data Warehouse Design considerations" on MSDN.
yikes

http://www.dwinfocenter.org/


rudy
http://r937.com/
Reply With Quote
  #3 (permalink)  
Old 06-27-03, 17:34
blindman blindman is offline
World Class Flame Warrior
 
Join Date: Jun 2003
Location: Ohio
Posts: 9,298
I've been designing databases and data warehouses in Access, Sybase and Microsoft SQL Server for 12 years, and I say screw the star model. It's fine for small, focused, datamarts, but as you've found out real data is much more complex than that. The "snowflake" schema is better, but I always start off with a fully normalized object-oriented data-modeling approach that provides maximum flexibility for storing and querying data. If your database starts approaching the multi-gigabyte size your queries will slow down, but by that time you will have a good understanding of how your data is being used and you can start pre-aggregating data or generating smaller datamarts from subsets of the data.
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On