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

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
jeffshieldsdev
Solution Sage
Solution Sage

Anyone have experience with Table.AddKey() ?

I just learned about this function a few weeks ago, and I’m wondering:

1) should I always be using this before my merges? (Where I’m not already doing Table.Distinct() obviously) One would assume the Power Query engine would do this kind of optimization automatically.

2) can one assume there’s always a performance benefit to adding keys to both sides of the merge? Or if my fact table is super long, should I just AddKey() on my dimension table?

Thanks!
1 ACCEPTED SOLUTION
Anonymous
Not applicable

According to Chris Webb's blog post, Table.AddKey() seems to help only on the "lookup side" of a join.

 

If you use Table.Distinct() on a single column of a table, then it will automatically add a key to that column.

 

It appears that the performance benefit only occurs when using Aggregation, not Expanding.

 

This appears to be because Power Query defaults to a full cartesian cross when joining 2 tables.  When you aggregate, you'll see a great performance improvement.

 

Also, if you're joining with the intention of expanding a column...and you're expecting a single value on the join, consider using aggregation.  You could use Min or First to grab that single value, and you should atill get the speed improvement.

 

Let us know what your results are!

 

View solution in original post

3 REPLIES 3
Anonymous
Not applicable

According to Chris Webb's blog post, Table.AddKey() seems to help only on the "lookup side" of a join.

 

If you use Table.Distinct() on a single column of a table, then it will automatically add a key to that column.

 

It appears that the performance benefit only occurs when using Aggregation, not Expanding.

 

This appears to be because Power Query defaults to a full cartesian cross when joining 2 tables.  When you aggregate, you'll see a great performance improvement.

 

Also, if you're joining with the intention of expanding a column...and you're expecting a single value on the join, consider using aggregation.  You could use Min or First to grab that single value, and you should atill get the speed improvement.

 

Let us know what your results are!

 

ImkeF
Community Champion
Community Champion

Kudos to @Anonymous  explanation.

 

If you want to aggregate the joined table, then there are some performance aspects to consider: https://www.thebiccountant.com/2019/10/28/performance-tip-for-aggregations-after-joins-in-power-query-and-power-bi/ 

 

But if you're joining distinct rows, then using the Key on the table is the only trick that I'm aware of.

In addition to that, make sure to check other factors that impact performance (especially the disabling of background refresh): https://www.thebiccountant.com/2019/10/28/performance-tip-for-aggregations-after-joins-in-power-query-and-power-bi/ 

 

Imke Feldmann (The BIccountant)

If you liked my solution, please give it a thumbs up. And if I did answer your question, please mark this post as a solution. Thanks!

How to integrate M-code into your solution -- How to get your questions answered quickly -- How to provide sample data -- Check out more PBI- learning resources here -- Performance Tipps for M-queries

Greg_Deckler
Community Champion
Community Champion

@ImkeF might have some thoughts.

 

You could experiment. The Tools tab of the Query Editor ribbon has diagnostics now.



Follow on LinkedIn
@ me in replies or I'll lose your thread!!!
Instead of a Kudo, please vote for this idea
Become an expert!: Enterprise DNA
External Tools: MSHGQM
YouTube Channel!: Microsoft Hates Greg
Latest book!:
DAX For Humans

DAX is easy, CALCULATE makes DAX hard...

Helpful resources

Announcements
July 2025 community update carousel

Fabric Community Update - July 2025

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

July PBI25 Carousel

Power BI Monthly Update - July 2025

Check out the July 2025 Power BI update to learn about new features.

Join our Fabric User Panel

Join our Fabric User Panel

This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.

Top Solution Authors