If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Cognos Planning 8.4.1 vs Cognos Planning 10.1

Started by isap, 04 May 2011 05:58:46 AM

Previous topic - Next topic

isap

I just started to work on Cognos Planning 8.4.1 since a week ago so have some questions about the latest version and features.......
What is the max for below?
Number of cubes: 
Number of Dlinks:   
Total number of cells in an application:
Largest Cube:
Total Number of d-list items in application:
Largest dimension:


Also - how can one achieve performance while running a large application? I read this somewhere on the posts "it's completely dependent on the design and configuration of the model and the various areas in the CAC that can define the applications structure. If you are not cutting things down with No Data Access tables and cut down models you wouldn't be able to reconcile."

Does it mean - cutting the application into smaller models or several cubes? how could CAC be helpful here? and finally "No Data Access tables" - isn't data access tables a way to manage user rights?

The above q's might sound a bit too basic but would appreciate all the responses. Thanks a lot in advance.


ericlfg

Hi Isap,

From the Planning Administration Guide, Page 67 that you can find here, 3rd PDF file in the list (for some reason I can't paste the link to the PDF directly)
https://www-304.ibm.com/support/docview.wss?uid=swg27019499

This will address your questions in red.  To address your other questions:

1.  Access tables are still relevant in 10.1, however, cut down models is deprecated (feature is no longer available).  No Data Access tables helps to address sparsity within the cubes and dimensions of an application and can be applied to specific e-list items.  I've seen very large applications work, but it's because the total number of cells per cube is reduced using no data access tables.  So as an example, a 2 million cell cube may only require 500,000 cells.  You would use no data access tables to trim 1.5 million cells out, making it smaller.

2. Generally the best practice is to build smaller applications (example: versions, or budgeting / forecasting years) and then use administration links to populate a summary application.   Using this method, you're building smaller applications that -should- perform better than one large application.

These are just my experiences and someone else may be able to address your questions more precisely.

Cheers

isap

Hey ericlfg - Thanks a lot for your quick response....your explanation helped me a lot to understand few concepts quickly and can apply now...Once again...Thanks.