With this link:http://pic.dhe.ibm.com/infocenter/cbi/v10r1m0/index.jsp?topic=%2Fcom.ibm.swg.im.cognos.ug_cra.10.1.0.doc%2Fug_cra_id9673ConcurrentQueryExecution.html
The performance is really impoved.
Without the concurrent setting, after I cancel the report, I could see the SQL is cancelled in the database side.
But with this setting, click the cancel button, Those SQLs are still running in the database side. I am not sure if this is a expected behavior. I tested several times and got the same. Which trace(UDA?) should I use to trace this cancel behavior to find if it is a cognos defect.
Any suggestion is welcome.
Ricky
Thanks.
UDA and CQE (Cognos Query Execution).