Skip to main content

PowerBI– How to fetch your data?

For an Azure Fabric based data platform we are building I'm evaluating PowerBI as a possible reporting solution. My knowledge of PowerBI is almost non existant so there are a lot of things I learned along the way.

My first lesson learned:

There are multiple ways to fetch data in PowerBI.

I learned this lesson quite fast when I tried to connect to my first datasource. After selecting the ‘Import data from database’ option I immediately got  to choose a Data Connectivity mode:


The available options were:

  • Import
  • DirectQuery

Let’s find out what each of these options mean and what exactly is the difference.

Import mode

This mode should be your first choice. As the name implies in this mode the data is imported in the report. When querying the data everything is loaded into memory which gives really fast query performance.

This sounds a good idea for really small datasets but what if you have a lot of data? PowerBI makes it possible to work with big datasets by compressing the data (a 10-times compression is not unusable). Storing it on disk makes it even more smaller.

This makes the import mode a good default for most datasets.

Remark: Be aware that the data is only as current as the latest refresh.

DirectQuery mode

A second mode is DirectQuery. When you use DirectQuery, the Power BI report does not store the data locally, which can be advantageous for scenarios where you want to ensure that the report always reflects the most up-to-date data from the source system. This is especially useful when dealing with large datasets that may be impractical to import into Power BI.

However, it's important to note that DirectQuery has some limitations and considerations. Not all data sources support DirectQuery, and the performance of your reports may depend on the speed and capabilities of your underlying data source. Additionally, some Power BI features may not be available or may behave differently when using DirectQuery compared to importing data.

Remark: There is also a third Composite mode that allows to mix Import and DirectQuery modes, or integrate multiple DirectQuery data sources. 

More information

Dataset modes in the Power BI service - Power BI | Microsoft Learn

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more