Dimension Table with Composite Key

[hunain]

I have a section table in my ERP. It contains sections for the courses offered. The columns part of composite key are term code and section. My question is should this be modelled as fact or dimension. if its dimension do i create something as section_key(surrogate) which will uniquely identify a section based on the natural key term code and section. Please also note that section is unique within a term so the same section can be used in another term. please advise. thanks.

[ngalemmo]

Yes, as a dimension the natural key would be term and section, it would resolve to a unique primary surrogate key. Such an arrangement is very common. As a dimension you would store attributes such as room, capacity, time, etc. The enrollment would be a fact that contains a FK to the dimension.