Anyone having performance issues with Jazz Reporting Service ?
I chatted with a user that is trying to use JRS and he relates that after trying to build a report, the application becomes unusable. He noticed that joins are poorly done ( e.g. all columns of joined tables are in the SQL, sometimes making the statement too large / complex )
CLM 5.0.2 ifix003
JRS:
Version: 5.0.2
Build ID: JRS_5.0.2-I20141028-2014
I have the ifix003, but it is not deployed, but didn't see much in the readme to give confidence that any fixes would help.
errors in rs.log:
CRRGW5628E An com.ibm.db2.jcc.am.SqlException error occurred when validating the input SQL s
tring, caused by [jcc][t4][10531][14103][4.14.121] The statement is too long or too complex. Current SQL statement size is 13,438,562. ERRORCODE=-101, SQLSTATE=54001.
How can this be good:
AND ((((((((((((((((((((((((((((((((((((((((t.PROJECT_ID = 7) OR (t.PROJECT_ID = 26
9)) OR
(t.PROJECT_ID = 247)) OR (t.PROJECT_ID = 106)) OR (t.PROJECT_ID = 211)) OR (t.PROJECT_ID = 120)) OR (t.PROJECT_ID = 38)) OR (t.PROJECT_ID = 42)) OR (t.PROJECT_ID = 21)) OR (t.PROJECT_ID = 27)) OR (t.PROJECT_ID = 50)) OR (t.PROJECT_ID = 199)) OR (t.PROJECT_ID = 54)) OR (t.PROJECT_ID = 53)) OR (t.PROJECT_ID = 58)) OR (t.PROJECT_ID = 26)) OR (t.PROJECT_ID = 177)) OR (t.PROJECT_ID = 117)) OR (t.PROJECT_ID = 79)) OR (t.PROJECT_ID = 98)) OR (t.PROJECT_ID = 82)) OR (t.PROJECT_ID = 60)) OR (t.PROJECT_ID = 85)) OR (t.PROJECT_ID = 81)) OR (t.PROJECT_ID = 100)) OR (t.PROJECT_ID = 88)) OR (t.PROJECT_ID = 63)) OR (t.PROJECT_ID = 70)) OR (t.PROJECT_ID = 80)) OR (t.PROJECT_ID = 76)) OR (t.PROJECT_ID = 262)) OR (t.PROJECT_ID = 151)) OR (t.PROJECT_ID = -1)) OR (t.PROJECT_ID = 201)) OR (t.PROJECT_ID = 181)) OR (t.PROJECT_ID = 22)) OR (t.PROJECT_ID = 93)) OR (t.PROJECT_ID = 176)) OR (t.PROJECT_ID = 221)) OR (t.PROJECT_ID = 222))
Wouldn't the IN predicate be better ?