SQL Database in Fabric — When OLTP Meets Your CU Budget

SQL Database in Fabric — When OLTP Meets Your CU Budget Episode 11 • 2026-03-13 Duration: 9:50 SQL Database in Fabric promises zero-ETL translytical architecture — OLTP writes mirrored to OneLake automatically. But the 15-minute billing window and interactive CU consumption change the math. We break down when it makes sense and when Azure SQL Database plus mirroring is the smarter play. What we discuss A real-world mistake from a pre-Fabric era The one question that reframes the architectural debate How we got here — predecessor products and evolution Why the "obvious" answer is often wrong A real Reddit/Microsoft Q&A question unpacked The concrete recommended architecture F-SKU realism — what this actually costs When the rejected approach is actually right Risks of the recommended path What Microsoft is shipping that changes the calculus The architectural principle to take home Key takeaways That's... a genuinely good architecture. For a lot of teams, that's the right call. You lose zero-config mirroring — you set it up manually — and you lose Git integration and the GraphQL API. But you gain VNet support, CDC, Always... Every. Single. Time. Plus the engine startup needs a two-gig minimum memory allocation. On an F2 capacity, that's... roughly your entire capacity eaten by one database. Technically — yes, that works. But the failure mode I asked about? It's cost. When you create a SQL Database in Fabric, two items appear — the database and a SQL analytics endpoint. Both consume interactive CUs. Not background —... Resources SQL database in Microsoft Fabric — Overview Mirroring Fabric SQL database Translytical applications with SQL database SQL database in Fabric tutorial — End-to-end architecture Data Factory SQL database connector GraphQL API for SQL database Mirroring limitations SQL analytics endpoint Automatic Tuning AI functions Fabric's CI/CD framework Limitations in SQL database in Fabric Feature comparison: Azure SQL Database and Fabric SQL database Billing and utilization reporting for SQL database Mirroring Azure SQL Database to Fabric About the show Built on ElevenLabs voice synthesis. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon. Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday. Submit your case Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing. Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.