Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more.
Get startedGrow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.
I have seen some solution already in here and on YouTube as well regarding creating Dim Table from a Fact Table in power query. The examples I have been have been anywhere from 100k to 300k rows Fact Table, right click on column need and create new query from there. My Fact Table is 9m to 10m rows depending on the number of months pulled. The SQL Query itself is not the fastest table to load. My question is should I create an additional table that is pulling distinct ids and names from that Fact Table or should I duplicate the Fact Table I am loading and remove other columns and duplicates. Looking to learn what the best practice for a large table should be for this request.
Thank you,
Solved! Go to Solution.
@SQL_SousChef Is your data source an actual SQL Query as in "SELECT * FROM 'Table'" or are you hitting a view or something? If it is, then it would be best to modify that query to just grab a single column because otherwise it will load your entire fact table twice.
@SQL_SousChef Is your data source an actual SQL Query as in "SELECT * FROM 'Table'" or are you hitting a view or something? If it is, then it would be best to modify that query to just grab a single column because otherwise it will load your entire fact table twice.
Thank you, yes it is a actual SQL Query where I can select the columns needed. Wasn't sure if that was the best practice or if I could just duplicate and remove the columns since I have the dataset already.
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Ask questions in Eventhouse and KQL, Eventstream, and Reflex.
User | Count |
---|---|
41 | |
30 | |
26 | |
21 | |
17 |