Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
influent
Constraint Violating Yak Guru
367 Posts |
 Posted - 2008-01-30 : 20:12:32
|
| I'm still fairly new to cubes, so bear with me. I'm trying to figure out if I should include aggregate data (e.g. total employees per facility) in a dimension table or if I should use the finished cube to get the counts (MDX?). Thanks for any help that you can provide.influent |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2008-01-31 : 00:07:46
|
| That depends on your requirement. You should decide n what grain of data you are interested in.Remember that you should always design cube with lowest grain that you require.So if you are interested in individual employee detail analysis you would want to store individual employee details in dimension. And your fact will link your employee dimension to get facility info which might be another dimension. The fact table will be containing all measures that you will interested in. The aggregations (total count of emp /facility) will be done and stored by cube itself ( while processing). You can also decide whether to prestore aggregated values in cude (MOLAP) or calculate it on the fly when you require (ROLAP). |
 |
|
|
|
|
|
aggregate data in dimension tables?