Learn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
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.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 6 | |
| 4 | |
| 3 | |
| 2 | |
| 2 |
| User | Count |
|---|---|
| 11 | |
| 10 | |
| 8 | |
| 7 | |
| 7 |