Report with too many joins and unions

[barrysaab]

This is might be off the topic,I am sorry,Still this question is bugging my mind for a while,Previously I had a chance to work in big organisation ,At least I thought the company FM model was poorly designed precisely for there were sales and Inventory data marts.Since reporting requirement were basically based on the fetching the data from both ,most of the reports were developed with quite a lot of joins and unions like MTD,YTD sales reports.The performance was understandably slow.I want to know ,Has other too came across this situation and how they dealt with it.Thanks

[bdbits]

Have you discussed your concerns with those who do the modelling? Have you researched it already so you have a better solution at hand when asked? And be prepared when you do ask that there may be valid reasons they cannot put them together.

If you are not able to communicate with the modeller, then you have an organizational problem. If managers are unwilling to listen, and you cannot live with that, you may need to consider other employers.

[barrysaab]

Thanks,The independent consultant who modeled the whole  applications were long gone then,management hadn't got a clue about Cognos so had no option but to move on.

[ravimahazan84]

In case you don't have option to talk with modeler or to change the modelling as per your requirement,you can work on optimization of your report design and queries.
Like you can use sub-queries in order to limit the data in your raw query.
you can change the processing to limited local in queries where join is involved.

Maximum use of key (integer) value while using the join operation.