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

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...
Read more