praveenj6

 Profile Answers by praveenj6 Questions by praveenj6

• Feb 4th, 2008

 

To increase the performance of a report while running
- set the governers
-joins shuld be less
-Aggregate table should be there while using group functions

there will be a dead lock while running a report against the OLTP database.so better not to do this

shailendra32

 Profile Answers by shailendra32 

• Aug 21st, 2012

 

1. Check that your query processing property is set to Database Only and not Limited Local.
2. There are Cognos functions and database functions (DB2 for example). Using one versus the other may make a difference in where the query processing takes place.

3. Certain things like distinct counts, search cases, and running functions force Limited Local processing. Try to avoid these when possible.
4. Use Local Caching.
5. In filters, refer to items in the database (full path name) rather than pulling everything into your query.
6. Use fixed column widths instead of dynamic column widths as much as possible.
7. Dont group items that dont need to be grouped. Use Level Span instead.
8. Set sorting at only one level in the query (i.e., not at query level and tabular model level both).
9. Use indexed columns as much as possible.
10. Check your SQL to confirm that the correct/expected tables are being pulled in, your joins are what you expect, and your filters are being coded properly.
11. Use as many filters as possible.
12. Move calculations into the model where possible so your query doesnt have to do them.
13. Place calculations judiciously so they are performed/reiterated as few times as possible.
14. Dont use scalar functions on indexed columns. This forces a full table scan.
15. . Use Boolean variables instead of String variables unless string variables are unavoidable. Boolean variables get executed faster as compared to String variables.