When to use CUT DOWN MODELS exactly in applications?

[Preethi]

Hi Folks,

I am very new to Cognos Planning, can anyone tell me the scenarios where exactly the importance of cutdown models will come.

And how they affect the performance?

Please, need help!

Thanks
Preethi. :)

[cbrandt]

Hi Preethi,

Welcome to Cognos Planning ;).
First of all there is a quite good long post about this topic in this forum and there is also good explanation in the contributor admin help.
Basically Cutdown only works in combination with nodata access tables. It will add a cut down job in the GTP process, but will reduce the model size for each elist. So the gtp will take longer but the model on the web will be smaller and faster for the end users.
A good example is cost planning, where you have cost centers as elist and accounts as dlist and you want to show only relevant accounts for each elist.

There are some exceptions for the performance impact which you will find in the CAC help.

Happy Planning!
Carsten

[sascha]

[...] will be smaller and faster for the end users. [...]

Hi cbrand,
I was just doing some investigation on different apps for my client and did some real tesing of timings having cut-down enabled vs. disabled. The result was that all 20 test cases did open up in the same time or even better (!) without using cut down models.
To my experience you'll always need to test and measure if this really saves time or only costs lots of database space.
Regards,
Sascha

[Gunes]

http://www.cognoise.com/community/index.php/topic,5604.0.html

This might of interest to you.

[Preethi]

Thanks a lot Carsten and Sascha. :)


Preethi