I've been looking at using a bridge solution to implement multi-valued attributes for a dimension in my data model (education information for a faculty member). I've seen two approaches used to implement this:
1. Chris Anderson on his blog (http://blog.oaktonsoftware.com/2011/01/resolve-repeating-attributes-with.html) proposes having a foreign key on the dimension table pointing to the bridge table. Using this approach, my model (simplified) will look as follows:
DimFaculty(FacultyKey, FacultyName, EducationGroupKey)
2. Shaun Ryan (http://brokenninja.wordpress.com/2011/05/05/multi-valued-attributes-in-sql-services-analysis-services-ssas/) and
Vincent Rainardi (http://dwbi1.wordpress.com/2011/03/13/dimensions-with-multi-valued-attributes/) instead proposes designs where bridge table only contains foreign keys to both the dimension and outrigger so my model would look as follows:
From an ETL and reporting viewpoint, which would be easier to implement?