Unable to run reports due to too large set size

Question

Hello guys
I am creating a report with almost 12 columns. I know it has a lot of data. When I tried to add one more column which is day column, it gives me the following errors:
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. Essbase Error: Internal error: Set is too large to be processed. Set size exceeds 2^32 tuples. (HY000)
SQL Issued: SELECT Brand."Brand Name" saw_0, Brand.Product saw_1, Offer."Offer Name" saw_2, "Subscription Offer_Cost"."Offer Cost" saw_3, "Continuity Cycle"."Cont Cycle" saw_4, "Acquisition Date"."Acquisition Month" saw_5, "Acquisition Date"."Acquisition Day" saw_6, "Retention Status".Status saw_7, Level."Subscription Leve" saw_8, SUM(CASE WHEN Level."Subscription Leve" = '0' THEN retntion."Count Of Orders" ELSE 0 END by "Acquisition Date"."Acquisition Month", Offer."Offer Name") saw_9, CASE WHEN Level."Subscription Leve" > '0' THEN retntion."Count Of Orders" ELSE 0 END saw_10, (CASE WHEN Level."Subscription Leve" > '0' THEN retntion."Count Of Orders" ELSE 0 END/SUM(CASE WHEN Level."Subscription Leve" = '0' THEN retntion."Count Of Orders" ELSE 0 END by "Acquisition Date"."Acquisition Month", Offer."Offer Name"))*100 saw_11 FROM retention_cube WHERE ("Acquisition Date"."Acquisition Month" BETWEEN '2009 Feb' AND '2009 Jan') ORDER BY saw_7 DESC
It's probably because the data size is too big for querry to return. Is there a way I can fix this error and still get the report with the new columns?
Any pointers will be greatly appreciated..

Answer 1

Well of course it is. (Set too large I mean)
SUM(CASE WHEN Level."Subscription Leve" = '0' THEN retntion."Count Of Orders" ELSE 0 END by "Acquisition Date"."Acquisition Month", Offer."Offer Name") saw_9,
CASE WHEN Level."Subscription Leve" > '0' THEN retntion."Count Of Orders" ELSE 0 END saw_10,
(CASE WHEN Level."Subscription Leve" > '0' THEN retntion."Count Of Orders" ELSE 0 END/SUM(CASE WHEN Level."Subscription Leve" = '0' THEN retntion."Count Of Orders" ELSE 0 END by "Acquisition Date"."Acquisition Month", Offer."Offer Name"))*100 saw_11
THAT is the way to kill a query going against Essbase. Just check out the MDX that generates in the background (i.e. read the log!) and try to fire that through SmartView. It will work until you hit a low grain on one of the dimensions. The time dimension being a perfect example.
Stuff like what you're trying to do should either be
- account members in Essbase,
- MDX EVALUATE_AGGR expressions in the RPD with the correct aggragation level set or
- MDX EVALUATE expressions in answers.
Push the number crunching and aggregating as far down the foodchain as you can. Everything will almost automatically result in failures.
Cheers,
Christi@n