Home > SQL Analysis Services > Thoughts Regarding “Kimball University: Five Alternatives for Better Employee Dimension Modeling”

Thoughts Regarding “Kimball University: Five Alternatives for Better Employee Dimension Modeling”

Today I read the article "Kimball University: Five Alternatives for Better Employee Dimension Modeling"

The basic employee dimension structure is quite common. However my personal opinion is that in most cases, employees change a lot while roles (company structure) are relatively stable. Hence, I prefer at the DW layer, separate the employees from the roles and make roles a self-referencing table. e.g. DimEmployee, DimRoles (or even DimEmployee, BridgeEmployeeRoles,Dimroles if you need many to many relationships). By doing this, when an SCD type 2 update from the top to bottom (let’s say CEO is changed) happens, you don’t have to replicate the whole tree. As even the person of CEO is changed, the position is not changed. People below CEO now is still under CEO. The only thing changed is that now the CEO is not XXX. He is YYY at the moment.

By the way, the Alternative 5: The PathString Attribute is quite interesting.

Advertisements
Categories: SQL Analysis Services
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: