Hi,

I'm looking for samples models for an HR model and specially the employee
dimension table.

What is better a slow changing dimension (with full history in the
dimension)?
or separate dimensions? I mean age, "current" organisation (or organization
unit), position etc... in separate tables.

Solution 1: maybe difficult to maintain
Solution 2: a lot of small tables

I'll create OLAP cubes for ad-hoc analysis & reports based on SQL
statements.
I know that I'll have dynamic distinct count formulas to setup in my cubes
(not the dcount aggregation one)

what are your recommendations?
any samples?

thanks.

Jerome.

Basically Employee dimension is a parent child dimension, which is
always a rapidly changing
You checking on the property "Changing" and see also BOL on the same.
They do fall under rapidly changing dimension rather than Slowly
changing dimension

Regards,
Prasanna