on 11-13-2006 10:32 PM
If I have 2 aggregates.. one for Jan and second for February and if I run a report for month range of Jan-Feb, I see that it does not hit the aggregate..So I assume that aggregate behaviour is same as Caching where the cache entries need to be a super set only in which we can use it properly..is this how aggregate is supposed to behave?
Ram,
ideally the query would look for an eggregate that matches the selection conditions that have been requested by the OLAP processor.
In your case , you have Aggregate 1 for Jan and Aggregate 2 for Feb and run the report for Jan and Feb which aggregate is the query supposed to hit ?
It would not pick the aggregate since the data required is spread across two aggregates and hence goes back to the cube , for it to hit an aggregate , :
1. Statistics help to a certain extent
2. build a proper hierarchy tree of aggregates starting with a basis aggregate so that the cube is not hit at any time and only the aggregate is hit.
Hope it helps..
Arun
Assign points if useful
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
your query might be having a variable to choose which month you are selecting for.
for this case if you hard code jan or feb and try to use a variable in query then i dont think it will match it against the defination of aggregate.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.