Forum Discussion
Fact / Dimensional Table Approach
I see what you mean.
I would look into separate bridge tables for bridge_track_artist (join on artist_id or artist) and bridge_track_genre (join on genre_id or genre). May require additional modeling work.
This would get rid of many to many but honestly, I'm not sure how much benefit you'll get from this, outside of knowing you've built a "best practice" model.
Community SupportHi vkedd ,
Thanks for reaching out to the Microsoft fabric community forum.
Thanks for your prompt response
I wanted to follow up and confirm whether you’ve had the opportunity to review the information provided. Should you have any questions or require further clarification, please don’t hesitate to reach out.
If you are still encountering any challenges, we would be more than happy to assist you further.
Thank you for being an active member of our community.
Best regards,
Lakshmi Narayana
Community SupportHi vkedd ,
If your issue has been resolved, please consider marking the most helpful reply as the accepted solution. This helps other community members who may encounter the same issue to find answers more efficiently.
If you're still facing challenges, feel free to let us know we’ll be glad to assist you further.
Looking forward to your response.
Best regards,
LakshmiNarayana.
- v-lgarikapat
Hi vkedd ,
As we haven’t heard back from you, we are closing this thread for now. If you are still experiencing the issue, please feel free to create a new thread we’ll be happy to assist you further.
Thank you for your patience and continued support.
If you found our response helpful, kindly mark it as Accepted as Solution so that others with similar queries can benefit from it.
Best regards,
Lakshmi Narayana