How to Refresh Only One Table in Power BI

Waiting for a massive Power BI report to refresh can feel like watching paint dry. If you're working with large sales tables, historical data, or complex data models, a full refresh can take anywhere from a few minutes to over an hour. This article will show you how to skip the wait by refreshing just a single table, saving you valuable time and resources.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Why Refresh a Single Table Instead of the Whole Dataset?

Before jumping into the "how," let's quickly cover the "why." Targeting a single table for a refresh isn't just a minor convenience, it's a strategic move that addresses several common pain points in data analysis and reporting.

• Significant Time Savings: This is the most obvious benefit. Imagine your dataset contains a massive, 10-million-row history table that rarely changes, but also a small, 5,000-row table of daily sales transactions that updates constantly. Refreshing the entire dataset forces Power BI to re-process all 10 million rows, even though nothing has changed. Refreshing only the daily sales table can cut a 30-minute process down to 30 seconds.
• Reduced Load on Data Sources: Every time Power BI runs a refresh, it sends queries to your underlying data sources, whether that's a SQL database, a SharePoint list, or an online API. Full refreshes can put a significant strain on these systems. By isolating the refresh to only the table that needs it, you lighten the load, keeping your database administrators happy and your systems running smoothly.
• Faster Development and Troubleshooting: When you're building a new report or trying to fix an issue, you need to iterate quickly. Waiting for a full refresh every time you make a small adjustment to a Power Query transformation is incredibly inefficient. A single-table refresh gives you instant feedback, allowing you to build, test, and debug at a much faster pace.
• Efficient Resource Management: Power BI Pro and Premium Per User (PPU) workspaces have limits on the number of scheduled refreshes you can perform per day (8 for Pro, 48 for PPU). By being more strategic with your refreshes, you can update different parts of your data at different frequencies without hitting these caps. It also reduces memory consumption and processing overhead on the Power BI service.

Method 1: The Quick and Easy Way in Power BI Desktop

This is the simplest and most direct method for refreshing a single table. It’s perfect for analysts and developers who are actively building or modifying a report within Power BI Desktop. Think of it as your go-to for quick updates and validation checks.

There are two primary locations where you can do this: the Model/Data view and the Power Query Editor.

From the Model or Data View

This is the fastest a la carte option when you just need to pull in the latest data for one table without going into the Power Query Editor.

Follow these steps:

1. Open your .pbix file in Power BI Desktop.
2. On the far left, click to enter either the Data view (the one that looks like a spreadsheet) or the Model view (the one with the relationship diagram).
3. On the right side of the screen, you will see the Data pane, which lists all the tables in your model.
4. Find the table you wish to update, hover your mouse over it, and click the three-dot menu (...) that appears.
5. From the context menu that pops up, select Refresh data.

Power BI will now connect only to the data source associated with that specific table and pull in the most recent data. You'll see a small loading dialog showing the progress for that one table. All your other tables will remain untouched.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

From within the Power Query Editor

You may prefer this method if you are already working on transformations and want to see the effect of a refresh on your query steps.

Follow these steps:

1. In Power BI Desktop, navigate to the Home tab on the ribbon.
2. Click on Transform data. This will open the Power Query Editor.
3. In the Queries pane on the left, you'll see a list of your tables.
4. Right-click on the table you want to refresh.
5. From the pop-up menu, select Refresh.

The query will run and your data preview within Power Query will update. This is especially useful for checking if a new column has appeared in the source or if recent changes are being pulled in correctly before applying all changes to your data model.

Limitation to Keep in Mind: This manual approach only works inside Power BI Desktop. It’s not a solution for automated refreshes on reports published to the Power BI Service.

Method 2: Splitting Datasets for Independent Refreshes in Power BI Service

Unfortunately, the Power BI Service does not offer a straightforward "refresh single table" button for scheduled refreshes. A scheduled refresh always targets the entire dataset. This is a common frustration, but there is a powerful architectural workaround: splitting your model into multiple, separate datasets.

The strategy is to group your tables based on their refresh frequency and publish them as distinct datasets in the same Power BI workspace. Then, you can use a feature called Composite Models to bring them all together in a single report.

Let's use an example. Your data model has:

• A FactSales table with millions of rows, which updates every hour.
• A DimProducts dimension table that updates nightly.
• A DimGeography dimension table that is static and only changes once a year.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Step 1: Create and Publish Separate Datasets

Instead of one large PBIX file, you’ll create several:

1. Sales Data Model (PBIX 1): Create a new Power BI file that contains only the FactSales table. Save and publish this to your desired Power BI workspace. Let's call this dataset "Sales Data".
2. Product Data Model (PBIX 2): Create another Power BI file that contains only the DimProducts table. Publish this to the same workspace. Let's call this "Product Data".
3. Geography Data Model (PBIX 3): A third file containing only the DimGeography table, also published as "Geography Data".

Step 2: Configure Independent Refresh Schedules

Now that you have three separate datasets in the Power BI service, you can give each one its own refresh schedule.

• Go to the settings for the "Sales Data" dataset and configure a scheduled refresh to run hourly.
• Go to the settings for the "Product Data" dataset and set it to refresh once per day.
• For the "Geography Data" dataset, you can either disable scheduled refresh entirely and refresh manually when needed, or set it for a yearly cadence.

Step 3: Build a Composite Model Report

The magic happens when you bring these separate sources together into a master report.

1. Open a new, blank Power BI Desktop file. This will be your final report file.
2. On the Home tab, click on Get Data and select Power BI datasets.
3. Select the "Sales Data" dataset from your workspace and click Connect. This creates a live connection.
4. You’ll see a warning that you're connected live. Click Make changes to this model. Power BI will tell you this will create a local model and switch the connection mode to DirectQuery — this is what you want.
5. Repeat step 2 and connect to the "Product Data" dataset, then to the "Geography Data" dataset.
6. Head to the Model view. You will see tables from all three datasets. You can now drag to create relationships between them (e.g., connect FactSales[ProductKey] to DimProducts[ProductKey]).

You can now build visuals using a combination of tables from your independently refreshing datasets. Your sales visuals will update hourly, while product information respects its daily schedule. You have effectively accomplished the goal of refreshing different tables at different rates.

Method 3: For Experts - XMLA Endpoints and Scripting

For organizations using Power BI Premium (per capacity or per user), there is an even more advanced method that provides granular control: using the XMLA endpoint.

The XMLA endpoint allows you to connect to your Power BI dataset with external tools as if it were an enterprise-grade database. Tools like SQL Server Management Studio (SSMS) and the community-favorite Tabular Editor can connect directly to your Power BI dataset in the cloud.

Once connected, you can use Tabular Model Scripting Language (TMSL) to execute precise refresh commands. For instance, you could execute a script that explicitly says:

{
  "refresh": {
    "type": "dataOnly",
    "objects": [
      {
        "database": "MyAwesomeDataset",
        "table": "MySingleTable"
      }
    ]
  }
}

This method gives you ultimate control and is a powerful tool for automation, especially when integrated into broader data pipelines using tools like Azure Data Factory. However, it requires a deeper technical understanding of the Tabular model and is generally reserved for BI professionals and data engineering teams working in a Premium environment.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

Final Thoughts

Refreshing an entire Power BI dataset is often unnecessary and inefficient. By using the right technique — whether it's a quick manual refresh in Power BI Desktop for development, an architectural shift to composite models for automated scheduling, or using advanced scripting via XMLA endpoints — you can save time, reduce strain on your systems, and build reports more effectively.

A big part of modern data analysis is finding smarter ways to work, not harder. Instead of spending hours wrangling datasets, splitting models, and managing complex refresh schedules, we created Graphed to simplify the entire process. Just connect your data sources in a few clicks, and instead of clicking through endless menus in Power BI, you can simply ask for what you need: "Show me my sales this month by product category." We instantly build a real-time dashboard that pulls live data automatically, removing the need to ever think about refresh schedules again.