Legacy DWH to Fabric: Hands-on Workshop with DataRiseLab
Capacity is the problem we run into most often with our clients, whether they're already on Fabric or getting ready to move. It maxes out at peak hours, the bill keeps creeping up, and reports are slow anyway. On 12 November we're running an online workshop on how to fix that.
What we'll cover:
🔷How Fabric works under the hood. Lakehouse, Warehouse, notebooks and Power BI share one OneLake and one capacity, which is why a heavy job in one corner drags everything else down.
🔷Pay-as-you-go vs. reserved. A one-year reservation saves around 40%, but you pay for it whether anything is running or not. We'll show the utilization level where each option wins, and when pausing capacity is worth it.
🔷Maxed-out capacity, slow reports. How to track down what's eating your CUs, and how to tell when scaling up solves the problem and when it just costs more.
🔷Excel on Direct Lake. A single pivot table can lock up an entire capacity; we've seen it freeze a client's capacity for a full hour. How to stop that from happening, and when Import mode is the better fit.
🔷Moving off SQL Server or Synapse. How we migrate legacy warehouses to Fabric with Cairn for Fabric. For one client, receipt aggregation went from 4 hours to 7 minutes.
Who's running it?
👤 Łukasz Lelwic, Solution Architect & Team Lead, AI & Architecture
👤 Paweł Jędrzejewski, Senior Business and Systems Analyst
Bring the Fabric problem that's been bugging you. We'll spend most of the time working through real cases from attendees. Free to join.