March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe 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
Hi all, data modelling question here.
I have a client with a large dataset where the main fact table is quite large (~1gb). We want to try doing a reload where we Import load the fact table up to a certain date (e.g. up to the end of last month) and then we would import a version of that fact table as a Direct Query for the newest data. The idea would be to keep increasing the Import load infrequently (once a month) but the Direct Query occurs daily. We would then append the Direct Query fact table to the Import load fact table during this process.
If we did this on the same table but append the Direct Query to it daily, does that mean reduced refresh times? Or does the fact that the Import Load version is changed mean that we will not improve refresh times?
Wondering if anyone has had experience with that before we go down the rabbit hole.
Solved! Go to Solution.
Hi @elcapitano ,
With import connection mode from the source will be loaded into Power BI. Loading in Power BI means consuming memory and disk space. As long as you are developing Power BI on your machine with Power BI Desktop, then it would be memory and disk space of your machine. When you publish the report into the website, then it will be memory and disk space of Power BI cloud machine.
DirectQuery is a direct connection to data source. Data will NOT be stored in Power BI model. Power BI will be a visualization layer, then query the data from data source every time. Power BI will only store metadata of tables (table names, column names, relationships…) but not the data. Power BI file size will be much smaller, and most probably you never hit the limitation of the size because there is no data stored in the model.
If you want more details about import and DirectQuery, please kindely refer to
DirectQuery, Live Connection or Import Data? Tough Decision! - RADACAD.
Best Regards,
Stephen Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @elcapitano ,
With import connection mode from the source will be loaded into Power BI. Loading in Power BI means consuming memory and disk space. As long as you are developing Power BI on your machine with Power BI Desktop, then it would be memory and disk space of your machine. When you publish the report into the website, then it will be memory and disk space of Power BI cloud machine.
DirectQuery is a direct connection to data source. Data will NOT be stored in Power BI model. Power BI will be a visualization layer, then query the data from data source every time. Power BI will only store metadata of tables (table names, column names, relationships…) but not the data. Power BI file size will be much smaller, and most probably you never hit the limitation of the size because there is no data stored in the model.
If you want more details about import and DirectQuery, please kindely refer to
DirectQuery, Live Connection or Import Data? Tough Decision! - RADACAD.
Best Regards,
Stephen Tao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
@elcapitano , 1 GB is not large. You should schedule incremental ETL and load it.
https://radacad.com/all-you-need-to-know-about-the-incremental-refresh-in-power-bi-load-changes-only
https://thinkaboutit.be/2020/02/how-do-i-implement-an-incremental-refresh-in-power-bi-free-or-pro/
The option you are taking is Hybrid Table
Refer video from Guyinacube -https://www.youtube.com/watch?v=HckuKYlx8kk
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.
User | Count |
---|---|
114 | |
76 | |
57 | |
52 | |
44 |
User | Count |
---|---|
168 | |
116 | |
63 | |
57 | |
50 |