Thank you for that info! Pentaho or just some open-source RDBMS is just the vague idea we have for now as we still struggle with the more fundamental questions of how to best model our data. Denormalization and cube-oriented star-schemas sound good on first sight, but there are a number of...
We are just in the planning and modelling phase to figure out which combination of modeling and tools would fit best. If at all possible, the preferred toolchain would be open source (e.g. Pentaho plus open source RDBMS).
We are aware of the sparsity problem, but despite the huge number of...
Thank you for this. Our situation is a bit different though: there is no single, well-defined set of reports but the very purpose of the the modelling should be to allow for a large number of very different ad-hoc reports that usually will compare different measurements (where the different...
I am still puzzled about the correct way to design a cube vs. several cubes so that reports and queries that compare several different measurements can be made as easily as possible. The problem is that when there are different measurements, these measurements may only share some dimensions or...
Thanks for that suggestion, but if I understand correctly this only helps in the case of having two dimensions. I would still have to issue another query in addition to the basic fact table query, but the second query (to figure out if with the current limitation on one dimension, the other...
The date was just an example. My interest is in some technique or tool that allows to generalize that idea. So no matter what combination of values for some j of n dimensions has already selected (date or other), none of those l dimensions of the k = n-j remaining dimensions (0 <= l <= k) where...
Thank you for your answer! At least it looks as if I am not missing something totally obvious here ... :)
Just to clarify: why I want is maybe a bit different as in your examples. The idea is to filter dimensions, not values of dimensions, in situations where that dimension is not applicable...
I would like to design a classic OLAP facts table using a star scheme. The SQL model of the facts table should be independent of any concrete RDBMS technology and portable between different systems.
The problem is this: users should be able to select subsets of the facts based on conjunctive...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.