Solved

Wide fact table vs. multiple fact tables

Posted on 2008-06-24
4
1,396 Views
Last Modified: 2013-11-16
I am currently developing a data warehouse for a telecom company.
We collect several different measures (100+) from the network elements on an hourly basis.
I'm wondering what the optimal data warehouse design would be:
1) Since all measures bear the same granularity (1 hour), and originate from similar network elements, it would make sense to put them all in the same fact table. I would therefore end up with a fact table composed of about 5 dimensions and 100+ fact fields. Does a 100+ field table sound like an acceptable design?
2) I could create several fact tables with each about 5 dimensions and each only a subset of the 100+ facts, grouped in a way likely to be queried by the end users. I would therefore have several fact tables with maximum 25 fact fields (which seems more reasonable?), but I would loose some flexibility in the sense that users could no longer query the data in ways that were unplanned or unexpected.
I would greatly appreciate any advice or comment or field experience with the 2 options proposed (or a 3rd alternative...).
0
Comment
Question by:optima-sc
  • 2
  • 2
4 Comments
 
LVL 19

Expert Comment

by:frankytee
ID: 21862022
would any user need to regularly access the 100 fields in a query?
fact tables should only contain related measures so i think option 2) is the way to go. group your measures by category into several fact tables.
just ensure that your fact tables can be joined together using a common id field etc or a "bridge"/mapping table
0
 

Author Comment

by:optima-sc
ID: 21863022
Well, I would not say that any user would need to 'regularly' access any of the 100 fields.
However, it is quite possible that, at certain points in time, they will need this kind of flexibility for troubleshooting a particular network element or do root cause analysis.
I guess the idea of grouping the facts by likely categories sounds good, however, isn't that potentially going to lead to very slow (and heavy) cross-table queries whenever more flexibility or unexpected analysis is needed from the end user?
0
 
LVL 19

Accepted Solution

by:
frankytee earned 500 total points
ID: 21863885
if you index your tables appropriately then you should get reasonable/good performance. and the only time you need to join the tables is when the user needs measures from both multiple fact tables which should be "infrequent" if the measures are not related. most data warehouse that i have seen have multiple fact tables not one huge one with 100 measures.
but dont take my opinion as gospel, create and test the 2 different models to see which one is better for you.
0
 

Author Comment

by:optima-sc
ID: 21868082
Well, after re-discussing this topic thoroughly with my client, it appears that the 'unexpected' queries might not be so infrequent. Since the wide fact table also has the advantage of simpler applications no matter what the end user choice is, we decided to go for that solution.
Thank you for taking the time to give me your advice, anyway. I'll award you the points.
0

Featured Post

Highfive Gives IT Their Time Back

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Using SQL Scripts we can save all the SQL queries as files that we use very frequently on our database later point of time. This is one of the feature present under SQL Workshop in Oracle Application Express.
Many companies are looking to get out of the datacenter business and to services like Microsoft Azure to provide Infrastructure as a Service (IaaS) solutions for legacy client server workloads, rather than continuing to make capital investments in h…
Video by: Steve
Using examples as well as descriptions, step through each of the common simple join types, explaining differences in syntax, differences in expected outputs and showing how the queries run along with the actual outputs based upon a simple set of dem…
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…

758 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now