MDX views, where / how are they evaluated?
Posted: Thu Sep 24, 2020 2:46 pm
Afternoon or the local equivalent,
I've an MDX view. It a level 0 view of a medium sized cube, not huge by any means, with a Filter applied to the cells based on the value of one of the measures in the cube. Fairly straight forward.
If I try and display the view in PAW I get an out of memory error
If I export the view in a TI it works in a couple of seconds with no issue.
Just curious as to what is going on here, any ideas? Is displaying an MDX view so different to ASCIIOutput that I shouldn't expect to get the same result?
With a normal view I'd expect this behaviour, a view that is too large to display can be exported in TI.
With an MDX view it seems to be behaving as if the core crossjoin before the filter is displayed must be small enough to display in order to display the results post filter. 82 rows returned in total post filter.
Cheers,
I've an MDX view. It a level 0 view of a medium sized cube, not huge by any means, with a Filter applied to the cells based on the value of one of the measures in the cube. Fairly straight forward.
If I try and display the view in PAW I get an out of memory error
If I export the view in a TI it works in a couple of seconds with no issue.
Just curious as to what is going on here, any ideas? Is displaying an MDX view so different to ASCIIOutput that I shouldn't expect to get the same result?
With a normal view I'd expect this behaviour, a view that is too large to display can be exported in TI.
With an MDX view it seems to be behaving as if the core crossjoin before the filter is displayed must be small enough to display in order to display the results post filter. 82 rows returned in total post filter.
Cheers,