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
Anonymous
Not applicable

What is more efficient for duplicating tables: referencing tables (PQ) or creating calculated tables

Sometimes, for some use cases, you want the same table to be available more than once in the model instead of using (in)active relations with USERELATIONSHIP. Eg. a Order Date and Shipping Date table.

 

You can do that by referencing a table (using PQ) or by creating calculated tables in DAX.

 

I wonder what is the most efficient approach regarding speed, size (memory) and refresh times?

1 ACCEPTED SOLUTION
Fowmy
Super User
Super User

@Anonymous 

Referencing the table in PQ is the best option. This way, when you load the queries to the model, you get a highly optimized model with good compression compared to creating Tables in the Model using dax

Did I answer your question? Mark my post as a solution! and hit thumbs up


Subscribe and learn Power BI from these videos

Website LinkedIn PBI User Group

View solution in original post

1 REPLY 1
Fowmy
Super User
Super User

@Anonymous 

Referencing the table in PQ is the best option. This way, when you load the queries to the model, you get a highly optimized model with good compression compared to creating Tables in the Model using dax

Did I answer your question? Mark my post as a solution! and hit thumbs up


Subscribe and learn Power BI from these videos

Website LinkedIn PBI User Group

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.