dimensional modelling

[tupac_rd]

Hi Gurus,

Is there a best practices document somewhere for creating a clean dimensional model in FM or otherwise from a relational model which has all kind of crazy joins, loops etc., I want to create more of a star schema kind of model..

Thanks
2pac

[Evorus]

2pac,

I can only go off what we've created, based on Dimensionally Modeled Data not a relational Database.
I will attempt to put this into a relational metadata perspective.

Within FM we have created 4 namespaces under the current project.

The Namespaces are as follows

Physical Metadata
This would be you relational metadata, I would also have a sub folder in here used to store your Query Subjects (Dimension and Facts etc.)
All your links are defined within this level


Consolidation View
This area is a copy of Physical Metadata you would like (The dimensions and facts etc)
There are no Joins within this level.
No surrogate keys should be brought accross

Dimensions
Utilise this level to create your Dimensional Higherarchy
Facts should be brought through to this level as well.

Business View
Create 2 folders one which contains shortcuts to your Analysis Dimensions and Measures (From the Namespace above)
And a Reporting folder which contains shortcuts to the Dimensions and Measures from the Consolidation View.

With this set up you will then have a set of Analysis Studio models and a Report Studio Models.


I would like to know if anyone else has a similar approach

E

[funkigreendog]

Hey 2pac,


I came across these articles the last couple of days which you may find helpful:

http://www.element61.be/e/resourc-detail.asp?ResourceId=7

http://www.ironsidegroup.com/2010/07/08/best-practices-in-cognos-8-framework-manager-model-design/

Hope they help.

Peter

[tupac_rd]

Thankyou very much. I will definitely look through them.

[MFGF]

2pac,

I can only go off what we've created, based on Dimensionally Modeled Data not a relational Database.
I will attempt to put this into a relational metadata perspective.

Within FM we have created 4 namespaces under the current project.

The Namespaces are as follows

Physical Metadata
This would be you relational metadata, I would also have a sub folder in here used to store your Query Subjects (Dimension and Facts etc.)
All your links are defined within this level


Consolidation View
This area is a copy of Physical Metadata you would like (The dimensions and facts etc)
There are no Joins within this level.
No surrogate keys should be brought accross

Dimensions
Utilise this level to create your Dimensional Higherarchy
Facts should be brought through to this level as well.

Business View
Create 2 folders one which contains shortcuts to your Analysis Dimensions and Measures (From the Namespace above)
And a Reporting folder which contains shortcuts to the Dimensions and Measures from the Consolidation View.

With this set up you will then have a set of Analysis Studio models and a Report Studio Models.


I would like to know if anyone else has a similar approach

E

Pretty much exactly how I'd do it too! :)