Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredGet Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
I have recently realised that the STAR schema is the recommended data model for power BI, and even the snowflake schema isnt the recommended approach
An event can have many details (Agenda items)
I guess its fine. See above, even when you drag the agenda items into the report is still only shows the two events.
Its when you want to know the number of agenda items in an event.
Basically, how would you go about transforming this into a STAR schema? And if you arent interested in measures against the drop down is it ok to leave it as a star schema?
you can denormalise (merge) the 2 dim event tables together .
it also always depends, on how much data you have etc. the issue around snowflake is the relationships, you need to have a good understanding if you for example are using bidirectional relationships. Always better to assess you needs against recommended
its not hard to denormalise though because the in-memory model compresses distinct data
Proud to be a Super User!
I still down know how I merge the two event table together though when it comes to the keys
I have no clue how to go about it. Do I then just have one ID in the Event dimension and have multiple rows for each event
I dont understand how this will work against the Fact table ?
So in the merged Event dim should I have
EventID AgendaID
1 1
1 2
1 3
1 4
And then you have the fact table joined to the Event ID?
Proud to be a Super User!
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
Check out the October 2025 Power BI update to learn about new features.