Feeder statement at the source cube is crashing the server

[anoops81]

Hi All ,

I have a dimension "Investment" which has 80,000 elements in it. I use a feeder statement in a look up cube which feeds data to the main cube. Because of this dimension , the feeder statement is not getting saved. When i put only a consolidation element in the feeder for that dimension, then it is working fine.

I wanted to know whether it will be possible to put a named subset of dimension elements in the feeder instead of !Investment. The main cube will be using only 4,000 elements in the Investement dimension. So I want to put only those 4,000 elements saved as a subset.


Regards
Anoop

[Cam]

hello,

what is a lookup cube?

you really need real time on a 80,000 dimension element cube? maybe something with TI can work faster and avoid longer waiting times in saving rules or crashing events.

Regards,

[anoops81]

Hi Cam ,

The lookup is actually a table with some values numeric values stored in it . This is for a reporting cube , which pulls the data from database .

I need to check on how to implement with TI . Some fields are editable to the user , so when they edit the number, they need to see the changes on the fly .


Regards
Anoop

[tomok]

the feeder statement is not getting saved

Probably due to overfeeding and running out of RAM. When you create a feeder statement you should only feed rule calculated cells that you know will evaluate to something other than 0. What is the condition that causes one of the 80,000 Investment elements to have a value in the reporting cube? Use that condition to do your feeding. I can't think of many situations where a lookup cube would be the source of a feeder. I'm not saying it can't be, just not likely to be the proper way.