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

Be one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now

Reply
adjrock
Frequent Visitor

Dropping table after merging

Hi all,

I'm quite new to Power Bi. Just wondering if there's a functionality to drop a table once you are done appending it to a main table that will be used in the data model? The benefit i look for is a cleaner data model to work with and potentially decluttering memory held by Pbi when in use. Appreciate any advise.

1 ACCEPTED SOLUTION
danextian
Super User
Super User

Hi @adjrock ,

 

I am assuming drop means not loading the query to the model. Right-click on the query that you have already appended then uncheck Enable load. The query will be grayed out and the name italicized once load has been disabled.disable load.png










Did I answer your question? Mark my post as a solution!


Proud to be a Super User!









"Tell me and I’ll forget; show me and I may remember; involve me and I’ll understand."
Need Power BI consultation, get in touch with me on LinkedIn or hire me on UpWork.
Learn with me on YouTube @DAXJutsu or follow my page on Facebook @DAXJutsuPBI.

View solution in original post

4 REPLIES 4
v-shex-msft
Community Support
Community Support

Hi @adjrock,

Nope, you can't drop these tables be caused merge function has referenced these tables.
For your requirement, I'd like to suggest you add some custom steps to store original source table and do merge operations, it does not require to reference other tables.

Old: not able to drop original tables.

 

Query1:
let
   Source='connector formula'
in
   Source

Query2:
let
   Source='connector formula'
in
   Source

Merge:
let
   Source=Table.Combine({Query1,Query2})
in
   Source

 

New: merge into one query.

 

let
   Source1='connector formula',//Query1
   Source2='connector formula',//Query2
   Merge=Table.Combine({Source1,Source2})
in
   Merge

 

Regards,

Xiaoxin Sheng

Community Support Team _ Xiaoxin
If this post helps, please consider accept as solution to help other members find it more quickly.

seems like the main table is getting updated despite the required tables being "Disabled" (unchecked Enable). Shouldn't the main ables fail then? Or is it loading old stale data. I suppose I can check but Power Query is so slow at the moment that I'm about to raise a support ticket if it exists 😄

HI @adjrock,

it seems like you turn off the loading option on original query tables.
In fact, your tables are being referenced by your merge table, so these tables still loading records for the merge operation. (they do not display in data model tables)

Any advanced operation added in your table? They will case the duplicate calculation and spend more memory resources.

Regards,

Xiaoxin Sheng

Community Support Team _ Xiaoxin
If this post helps, please consider accept as solution to help other members find it more quickly.
danextian
Super User
Super User

Hi @adjrock ,

 

I am assuming drop means not loading the query to the model. Right-click on the query that you have already appended then uncheck Enable load. The query will be grayed out and the name italicized once load has been disabled.disable load.png










Did I answer your question? Mark my post as a solution!


Proud to be a Super User!









"Tell me and I’ll forget; show me and I may remember; involve me and I’ll understand."
Need Power BI consultation, get in touch with me on LinkedIn or hire me on UpWork.
Learn with me on YouTube @DAXJutsu or follow my page on Facebook @DAXJutsuPBI.

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!

ArunFabCon

Microsoft Fabric Community Conference 2025

Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.

December 2024

A Year in Review - December 2024

Find out what content was popular in the Fabric community during 2024.