We all know that implementing best practices at FM is very important as all reports/cubes/metric designer are dependent on it.
We may not follow best practice at report studio or analysis studio level as these things don't have any other objects which are dependent on them.
But at cube and at FM and at metric designer it is imperative to follow best practice.
Let us discuss PRACTICALY best practice at FM level.
Create following layers
Data layer - vanilla database table objects , no joins at this layer. Define the query items property here so that following layers can inherit that.
Business layer - crate joins and determinants and give business names to query items.
Dimension leyer - if you are doing a DMR.
Presentation layer or short cut layer - better you call it a short cut layer so that you know you have to use short cut here , you might want crate star schema groupings here if required.
If there is a confirmed dimension that lies in 2 star schema grouping better you make join again at presentation layer b/w short cuts so that cognos can do stitching .
Thank You,
Vishwas Gupta
We may not follow best practice at report studio or analysis studio level as these things don't have any other objects which are dependent on them.
But at cube and at FM and at metric designer it is imperative to follow best practice.
Let us discuss PRACTICALY best practice at FM level.
Create following layers
Data layer - vanilla database table objects , no joins at this layer. Define the query items property here so that following layers can inherit that.
Business layer - crate joins and determinants and give business names to query items.
Dimension leyer - if you are doing a DMR.
Presentation layer or short cut layer - better you call it a short cut layer so that you know you have to use short cut here , you might want crate star schema groupings here if required.
If there is a confirmed dimension that lies in 2 star schema grouping better you make join again at presentation layer b/w short cuts so that cognos can do stitching .
Thank You,
Vishwas Gupta
No comments:
Post a Comment