Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowData Days is here! Join us now for 60+ days of learning, challenges, and connection. Learn more
1 Week to powerBI and I'm loving it! I'm preparing an attrition report for my company and is attending udemy course and youtube video.
In this video, I saw the guy segrating the information from his masterfile to different table like Position has its own data table, Leavers , Joiners, Location etc., and connect all this data in the data model. I'm curious if this is the way to go or having all this information in one data table is okay because that's what I have so far.
Thanks!
Solved! Go to Solution.
It is ok, as long as you dont encounter some performance or memory issues. The reason all the modeling is done is, in my opinion, because
a) in case of big data, partly normalized tables are more effective and
b) you commonly get the data in many tables way from your database, so you can either merge or model...
So unless your data source is causing any problems, you are good to go with it.
It is ok, as long as you dont encounter some performance or memory issues. The reason all the modeling is done is, in my opinion, because
a) in case of big data, partly normalized tables are more effective and
b) you commonly get the data in many tables way from your database, so you can either merge or model...
So unless your data source is causing any problems, you are good to go with it.
Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.
Check out the May 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 4 | |
| 4 | |
| 3 | |
| 2 | |
| 1 |
| User | Count |
|---|---|
| 11 | |
| 11 | |
| 5 | |
| 4 | |
| 4 |