What is Enable Load in Power BI?

If you've ever dealt with a slow-running Power BI report or a file so large it takes forever to open, you know the frustration. Optimizing your report’s performance often comes down to managing your data model efficiently. This guide explains a small but powerful feature inside the Power Query Editor called "Enable Load," showing you how to use it to make your Power BI reports faster, smaller, and easier to manage.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Understanding the Power Query Editor Environment

Before diving into "Enable Load," it helps to quickly recap where it lives. Power BI’s real data transformation magic happens in the Power Query Editor. You get there by clicking the "Transform data" button on the Home ribbon. This is your workshop for cleaning, shaping, and preparing all the data before it ever appears in your report visuals.

On the left side of the Power Query window, you’ll see the "Queries" pane. Each item in this list represents a table or a set of instructions for getting data. Power Query processes each query step-by-step to produce a final table of data. The "Enable Load" feature determines what happens to that final table.

What is "Enable Load" in Power BI?

By default, every new query you create in Power BI has "Enable Load" checked. This setting tells Power BI one simple thing: "Take the final output of this query and load it into the Power BI data model."

But what does "loading into the data model" really mean? It means the data is:

• Stored in Memory (RAM): The data from the query is compressed using the VertiPaq engine and stored in your computer's memory when you work with the file. This is what makes Power BI visuals so fast and interactive.
• Saved in the .PBIX File: The data becomes part of your .pbix file, increasing its size.
• Visible in the Report View: The query appears as a usable table in the "Data" pane of your Report View, ready to be dragged into visuals and used in DAX calculations.

When you uncheck "Enable Load," you’re telling Power BI: "Go ahead and execute this query as part of the data refresh process, but do not load its final output into the data model." The query still runs in the background, but its data is not stored in memory or saved within the file. It effectively becomes a behind-the-scenes helper.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

When Should You Disable "Enable Load"?

Disabling the load might sound counterintuitive - why would you import data just to tell Power BI not to use it? The answer lies in building an efficient data preparation workflow. You should disable "Enable Load" for any query that is not a final, clean table needed for your report visuals.

This includes intermediate transformation steps, queries used for merging, and custom functions.

Scenario 1: Staging or Intermediate Queries

This is the most common and powerful use case for disabling "Enable Load." Often, you need to combine data from multiple sources or perform a series of complex cleaning steps. You might build queries that serve as "staging" tables - they aren't the final product, but they are essential parts of the assembly line.

Example: Consolidating Regional Sales Data

Imagine you have separate sales data files for three different regions: North America Sales, European Sales, and Asia Sales. You import each one as a separate query.

Your goal is to create a single, unified table called Global Sales that contains all the data. To do this, you create a new query that appends the three regional queries together.

1. Query 1: North America Sales
2. Query 2: European Sales
3. Query 3: Asia Sales
4. Query 4: Global Sales (created by appending Queries 1, 2, and 3)

In your final report, you only need the Global Sales table. The individual regional tables are redundant. If you leave "Enable Load" on for all four queries, you are chewing up three times more memory than necessary and cluttering your data model with tables you'll never use in visuals.

The Solution: In the Power Query Editor, you would right-click on the North America Sales, European Sales, and Asia Sales queries and uncheck "Enable Load." You leave it checked for the final Global Sales query. Now, only one table gets loaded into your model, making your report far more efficient.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

Scenario 2: Helper Queries for Merging or Filtering

Sometimes you need a query just to help another query. For instance, you might use a table as a filter or to add a column during a merge operation. Once that operation is done, the helper query has served its purpose and doesn’t need to take up space in your model.

Example: Filtering an Employee List

Let's say you have a master query with All Employees from your HR system. Your manager gives you an Excel file with a list of employees who have recently completed a training program (Trained Employees). You need to create a final report focused only on that group.

You can use a "Merge as Inner Join" operation between All Employees and Trained Employees to filter your main list.

The Trained Employees query is just a "helper" here. Its only job is to provide the list of names for filtering. You don't need a separate "Trained Employees" table cluttering up your data model, as the final, merged query contains all the information you need.

The Solution: After performing the merge, you disable "Enable Load" for the Trained Employees query. It will still refresh and provide its data to the main query during a refresh, but it won’t appear as a standalone table in your report.

Scenario 3: Custom Functions and Parameters

If you get into more advanced Power Query development, you might create custom M functions or queries that hold parameters. These are pure logic and a single parameter value - they are not tables of data. Therefore, they should never be loaded into the data model.

The Solution: Always disable "Enable Load" for queries that are functioning as custom functions or parameter lists.

Graphed

Still Building Reports Manually?

Watch how growth teams are getting answers in seconds — not days.

Watch the Demo

The Key Difference: "Enable Load" vs. "Include in Report Refresh"

Right next to the "Enable Load" option in the right-click menu, you'll see "Include in Report Refresh." Newcomers often confuse these two, but they control very different things.

• Enable Load: Decides if the query's output gets loaded into the semantic model (and uses memory).
• Include in Report Refresh: Decides if a query will be executed when you click the "Refresh" button.

Think back to our regional sales example. We disabled "Enable Load" for the three regional queries. But should we also disable "Include in Report Refresh"?

Absolutely not.

The final Global Sales query depends on data to flow from the three regional queries. If you stop the regional queries from refreshing, your Global Sales query will get no new data. It will be performing an Append operation on stale, old data cached from the last run.

Here's the rule of thumb:

If a query is used as a source for another query (via merging, appending, or referencing), you **must** keep "Include in Report Refresh" enabled for it, even if you disable "Enable Load."

If you don’t, your data pipeline breaks.

How to Disable "Enable Load": A Step-by-Step Guide

Applying this is simple. Follow these steps inside the Power Query Editor:

1. Open the Power Query Editor: On the "Home" tab in Power BI Desktop, click "Transform data."
2. Locate Your Query: In the "Queries" pane on the left, find the query you want to use as an intermediate step (e.g., one of our regional sales tables).
3. Right-Click a Query: Right-click on the query name to bring up the context menu.
4. Uncheck "Enable Load": In the context menu, you’ll see that "Enable Load" is checked by default. Simply click it to uncheck it.
5. Notice the Italicized Font: You'll immediately see the query's title in the list turn to italics. This is a helpful visual cue from Power BI indicating that the query is not scheduled to be loaded into the data model.
6. Click "Close & Apply": In the top-left corner, click "Close & Apply." Power BI will apply your changes. When it’s done, you'll notice that the table you modified no longer appears in the "Data" pane of your Report View. Success!

The Impact: Better Performance and a Cleaner Model

Taking a few seconds to right-click and disable load on staging queries might seem small, but it has a massive cumulative effect on complex reports. The benefits are clear:

• Reduced File Size: By preventing unnecessary data from being saved inside your .pbix file, you keep your files leaner and easier to share.
• Faster Refresh Times: Power BI doesn't have to waste time reloading and compressing every single intermediate data table into the model. The refresh process becomes much more focused on only the final tables you need.
• Lower Memory (RAM) Consumption: This is huge. Less data in the model means lower RAM usage, making your report much faster for both yourself during development and for end-users who are interacting with it. For very large datasets, this can be the difference between a usable report and an unusable one.
• A More Organized Data Model: When you look at your Data pane or the Model View, you will only see the final, cleaned-up tables. You won’t see dozens of intermediate tables cluttering up your workspace, making it much simpler to create relationships and write DAX measures.

Final Thoughts

Properly managing your queries using "Enable Load" is a fundamental skill for moving from a beginner to an intermediate Power BI developer. By consciously deciding which queries are final "reporting" tables and which are merely "helper" steps in your data preparation pipeline, you can build reports that are faster, smaller, and significantly easier to maintain over time.

Wrestling with data models and technical settings like this is often the most time-consuming part of analytics. Though powerful, BI tools introduce complexity that can slow everyone down. At Graphed, we help you sidestep that entirely by connecting directly to your marketing and sales platforms (like Google Analytics, Shopify, Facebook Ads, and Salesforce). Instead of manually transforming queries on your desktop, you can create real-time dashboards and get answers instantly by simply describing what you want to see - no complex settings or learning curve required.