![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi, My fact table contains 1 year's data. But the first 6 months needs one set of dimensions and the next 6 monthts need a different set of dimensions. So, if I build a cube containing the 1 year's data and all the dimensions, can I build two virual cubes, one with the first 6 months and the other with last 6 months of data ? How ? I have not been able to figure out how to restrict data. Can we do this at all (like the view of a relational table ?) Thanks a lot. |
#3
| |||
| |||
|
#4
| ||||
| ||||
|
|
This brings up an excellent question - I know virtual cubes can be used to allow the particular cubes to contain a subset of the measures, but can it |
|
i.e., Measures M1, M2, M3, M4 and M5. Dimensions D1, D2, D2, D3, D4, and D5. I know its easy to have 2 cubes Cube1: M1, M2 + D1, D2, D3, D4, and D5 Cube2: M3, M4, M5 + D1, D2, D3, D4, and D5 Then, if you bring them together its the same as if you just had everything in one cube. Now - what I want to do is have: Cube1: M1, M2 + D1, D2, D3 Cube2: M3, M4, M5 + D3, D4, and D5. I've found the statement "Virtual cubes must have one dimension in common". So, what if we add a primary key to the fact table, and use that |
|
Cube1: M1, M2 + DPK, D1, D2, D3 Cube2: M3, M4, M5 + DPK, D3, D4, D5 Thus each 'event' (like a sale at a store) would have a primary key and the dimensions (salesperson, storeid, etc.) and the facts (price, |
|
What do you think? |
![]() |
| Thread Tools | |
| Display Modes | |
| |