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 nowJuly 7 - July 17 | Round 2 of the Power BI Dataviz World Championships. Don't miss your chance! Learn more
Here is a picture illustrating my scenario:
I read that the proper relations between the two source is the key but I don't know how to connect these two different sources.
If I try to merge the two tables in one - is this a good approach...I will have table with 250K recoords.
Can anyone advise me what is the recommended approach is such scenarios?
Solved! Go to Solution.
@DimchoTsanov
The best practice and approach is to create separate dimension tables, either in SQL or Power Query. For example, you can create a single date table and link to both the source data tables using the One-To-Many relationship.
Follow the same for the other columns that are common in both tables.
⭕ Subscribe and learn Power BI from these videos
⚪ Website ⚪ LinkedIn ⚪ PBI User Group
@DimchoTsanov
The best practice and approach is to create separate dimension tables, either in SQL or Power Query. For example, you can create a single date table and link to both the source data tables using the One-To-Many relationship.
Follow the same for the other columns that are common in both tables.
⭕ Subscribe and learn Power BI from these videos
⚪ Website ⚪ LinkedIn ⚪ PBI User Group
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
Join Fabric Data Days 2026: 60 days of free live/on-demand sessions, challenges, study groups, and certification opportunities.
| User | Count |
|---|---|
| 22 | |
| 22 | |
| 18 | |
| 16 | |
| 13 |
| User | Count |
|---|---|
| 63 | |
| 42 | |
| 40 | |
| 40 | |
| 40 |