Framework Manager Advice

[msanders]

When taking the Framework Manager Class from Cognos.  When setting up Famework you should have a:

Presentation Layer
Database Layer

After working in FMgr for sometime now,  I have come to the conclusion that the Database Layer is not really needed because all our joins and calculation are done in the Presentation Layer. 

I tested this out and all the reports work fine and Query Subject and Query Items have reduced in size.  This Model use to take 20 minutes to save. now I have reduced it to about 1 minute by stripping out the database layer and a few tables that are not being used in the packages.

Question:  Is taking the Database Layer out a good idea or am I setting myself up for problems

[MFGF]

Hi,

Did you take the Part 2 Metadata Modeling class from Cognos too?  This actually suggests a 3-tier approach - Data Source View, then Virtual Star Schema View, then Presentation View.

Generally the calculations, filters etc would be added at the Data Source View level, and all relationships and query items would need to be checked here.
The Virtual Star Schema View level is added on top to resolve things like unwanted query splits and blind spots (in other words to provide accurate, consistent results from the reports).
The Presentation View would normally comprise mostly of shortcuts back to the Virtual Star Schema View - Star Schema Groupings ideally.

In my experience, if you don't follow this kind of modeling strategy you can get some very weird queries generated by your studios - I'd recommend you stick with Cognos's advice here, or you may get big problems later.

Regards,

MF.