Hello !
Going from mondrian 3.3 to 3.5 brought a strange phenomenon.
First, some query take 5X the time to execute. Looking at the mondian SQL log, I noticed that some query are unsing the IN clause with only 8 members at a time, repeting the SELECT to include all the 800+ value:
Ex.:
SELECT ...
AND DeptCode IN (1,2,3,4,5,6,7,8)
...
SELECT ...
AND DeptCode IN (9,10,11,12,13,14,15,16)
...
My mondrian.rolap.maxConstraints parameter is set at 1000. I tried increasing it to 10000 with no changes.
Is this parameter still used in 3.5 ? Why do I only get 8 values per IN clause ?
Database: SQLServer 2008
Thanks !
Going from mondrian 3.3 to 3.5 brought a strange phenomenon.
First, some query take 5X the time to execute. Looking at the mondian SQL log, I noticed that some query are unsing the IN clause with only 8 members at a time, repeting the SELECT to include all the 800+ value:
Ex.:
SELECT ...
AND DeptCode IN (1,2,3,4,5,6,7,8)
...
SELECT ...
AND DeptCode IN (9,10,11,12,13,14,15,16)
...
My mondrian.rolap.maxConstraints parameter is set at 1000. I tried increasing it to 10000 with no changes.
Is this parameter still used in 3.5 ? Why do I only get 8 values per IN clause ?
Database: SQLServer 2008
Thanks !