Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Reply
arock-well
Helper V
Helper V

Merging Queries: Dataflows vs Datasets?

I realize that normalized star/snowflake schemas are usually the best way to go in terms of efficiency and performance. However, I have a situation where I have six tables (one fact, six dimension) and I want to create into one big flat table.

 

In terms of merging these tables, is there any benefit when it comes to efficiency and refresh performance to do this in a Dataflow or later on in a Dataset? 

6 REPLIES 6
parry2k
Super User
Super User

@arock-well there are many reasons but 2-3 top would be: 1) it will take less time to refresh since data is already processed in the dataflow 2) better compression 3) dataflow processed data can be used in multiple Power BI reports 



Subscribe to the @PowerBIHowTo YT channel for an upcoming video on List and Record functions in Power Query!!

Learn Power BI and Fabric - subscribe to our YT channel - Click here: @PowerBIHowTo

If my solution proved useful, I'd be delighted to receive Kudos. When you put effort into asking a question, it's equally thoughtful to acknowledge and give Kudos to the individual who helped you solve the problem. It's a small gesture that shows appreciation and encouragement! ❤


Did I answer your question? Mark my post as a solution. Proud to be a Super User! Appreciate your Kudos 🙂
Feel free to email me with any of your BI needs.

Thank you!

parry2k
Super User
Super User

Well in that case (for whatever reason) I would recommend it to do in dataflow. 



Subscribe to the @PowerBIHowTo YT channel for an upcoming video on List and Record functions in Power Query!!

Learn Power BI and Fabric - subscribe to our YT channel - Click here: @PowerBIHowTo

If my solution proved useful, I'd be delighted to receive Kudos. When you put effort into asking a question, it's equally thoughtful to acknowledge and give Kudos to the individual who helped you solve the problem. It's a small gesture that shows appreciation and encouragement! ❤


Did I answer your question? Mark my post as a solution. Proud to be a Super User! Appreciate your Kudos 🙂
Feel free to email me with any of your BI needs.

Thanks! Are there particular reasons why you'd go the dataflow route vs dataset? 

parry2k
Super User
Super User

@arock-well first question, why a flat table if you have a proper star schema, you can potentially run into challenges using one flat table, and also it is not the best practice.



Subscribe to the @PowerBIHowTo YT channel for an upcoming video on List and Record functions in Power Query!!

Learn Power BI and Fabric - subscribe to our YT channel - Click here: @PowerBIHowTo

If my solution proved useful, I'd be delighted to receive Kudos. When you put effort into asking a question, it's equally thoughtful to acknowledge and give Kudos to the individual who helped you solve the problem. It's a small gesture that shows appreciation and encouragement! ❤


Did I answer your question? Mark my post as a solution. Proud to be a Super User! Appreciate your Kudos 🙂
Feel free to email me with any of your BI needs.

As I already mentioned in the original message, I realize that is the best way to go. I'm not going to go into the reasons.

 

So based on that, what would be the best way to do merges: Within a dataflow or dataset?

Helpful resources

Announcements
Europe Fabric Conference

Europe’s largest Microsoft Fabric Community Conference

Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.

AugPowerBI_Carousel

Power BI Monthly Update - August 2024

Check out the August 2024 Power BI update to learn about new features.

August Carousel

Fabric Community Update - August 2024

Find out what's new and trending in the Fabric Community.