Hi,
we can do the performance tuning in Cognos configuration,Frame work manager,Cognos connection and Report studio level.In report studio we can use limited local,use local cache yes and by using some static choices in prompt page we can improve the performance except this is their any options available in report studio?
Regards,
Anand.
The best report tuning is understanding the sql being fired off to your database. If you can optimize what a report is doing, then this is most likely your biggest advantage. We used the audit tables to see the exact SQL being sent to oracle. We would then run it straight against the database to see what it was doing.
By going through this exercise we took several minute running reports down to seconds by writing the report in such a way that the following was achievable:
1)Better generated SQL through the database friendly prompts (sending prompt data in a format that agreed with the database -- time prompts were key)
2)Reducing the number of queries and sub queries written by obtaining more data in fewer SQL executions
3)Identifying reusable elements for repeater tables, report headers and footers, and rewriting of several list items into one crosstab.
This is just one exercise that was beneficial to our organization.
We are going through the same concept with Framework at this time. We have learned in a few instances that views could be utilized to write better sql than the tool is. this does require some overhead as now you have another database component to worry about, but our gain has been greater from it.
Just some thoughts.