Listen in the Podli app 🎧
Follow your favourite podcasts, listen offline and in the car with CarPlay and Android Auto, and always pick up where you left off. Free to try.
Power BI used to force a choice between fast but stale import reports and fresh but slow DirectQuery. This episode explains Direct Lake in Microsoft Fabric for analysts and admins who want both. You learn how framing works, which of the two flavours to pick, what licensing it needs and which mistakes make it slow.
In this episode- 00:00 – Why fast and fresh rarely happen together
- 02:15 – What Direct Lake actually is
- 04:31 – How it works under the hood
- 06:49 – The two flavors of Direct Lake
- 08:59 – Where Direct Lake fits in the Microsoft stack
- 10:42 – Mistakes that make Direct Lake slow
- 13:10 – What to remember
Key takeaways- Direct Lake lets Power BI read Delta tables straight from OneLake, combining import-like speed with data that stays close to live.
- A Direct Lake refresh is called framing: it only updates pointers to the newest files, while transcoding loads just the columns a query needs.
- Direct Lake requires a paid Fabric capacity and rewards tidy Delta tables, so overwrites, tiny files and poor partitioning make it feel slow.
Worth quoting“A stale number doesn't announce itself. It looks exactly like a fresh one, and someone makes a decision on it before anyone notices.” – Mirko Peters (01:28)
“Instead of dragging your data into the report, direct lake points the report at those files and reads them where they sit.” – Mirko Peters (03:02)
Explore more on M365.FMFollow and rate M365.FM in your podcast app, and join the free M365 community at m365con.net.
Become a supporter of this podcast:
https://www.spreaker.com/podcast/m365-fm-microsoft-365-azure-cloud-power-platform-ai--6704921/support.
This episode includes AI-generated content.
