Trauma with query reuse

[garfunkal]

Hiya

I've got some problems with a report a customer wanted.  I guess its basically a dashboard type report -  It has in it about 30 KPIS, and these are split between 8 distinct crosstabs.  Each row has a microchart in it for KPI trends.  Initially I had used a Framework Model which referenced the tables, buit I noticed it was querying twice per row.  I changed the FM model to instead use a stored Procedure, and I unioned each row into it.   This meant that it LOOKED like the report on ran the procedure once.

It seems not - I put an insert into a table in the proc, and it looks like its still firing once per KPI, which means that the report takes about 15 seconds.  This, apparently, is unacceptable, and so i need to speed it up. 

Is there anything I can do - I've tried to set concurrent use and local cache - am I missing something or is their request unreasonable given the requirement?

I've attached an image of the report - obv i've taken out the branding and the numbers... i dont want to lose my job hey!

Any help gratefully accepted

Cheers - Andrew

[rockytopmark]

Setting Query Processing to Concurrent also requires that this feature is turned on in the Cognos Configuration.  If not, that setting change on the report queries will not make any difference.  Search IBM's Cognos KB, there are articles that describe the process to activate it.

15 seconds for 30 KPIs, including trending graphs... isn't too shabby as it is.  Good Luck figuring out ways to improve that!!

[blom0344]

Andrew,

15 seconds looks pretty fast to me !  If this is unacceptable, I wonder whether your client has any association with the stock exchange?

What a silly demand!!

[charon]

15 sec...what the fxxx
dude, if you want to get faster reports hardcore any imaginary numbers :D
(ive created a reports last month, based on dmr and using 6 fact tables, which run for about 7-8 hours ;) some etl work helped but still..15 sec..   :P
cheerz