Accelerate insights with real-time Azure SQL data and Microsoft Fabric
summary
Mirroring copies Azure SQL Database (initial snapshot + incremental changes read from the transaction log) into Microsoft Fabric’s OneLake so analytics run against near real-time data without touching the operational DB, using zero ETL and free replication compute. Latency targets are high single‑digit minutes for change propagation; mirrored storage is free up to your capacity (example: 64 TB free mirrored storage with 64 capacity). DDLs (add/alter/drop columns) are supported while mirroring runs; CDC and mirroring both read the log and can’t run simultaneously.
AI-written summary · about
chapters (8)
- 0:00Fabric mirroring for Azure SQL
- 3:37Fabric mirroring solves sprawl
- 10:04Setting up mirroring in Azure SQL
- 14:36Mirroring vs CDC explained
- 21:16Exploring mirrored data in Fabric
- 29:22Mirroring benefits and roadmap
- 37:04Archiving SQL data with Fabric
- 42:17Q&A on security
related talks
15mNear real-time analytics on Azure Cosmos DB with Microsoft Fabric mirroring
25mAzure SQL MI & Fabric Fusion: A speed-session
51mA Deep Dive into Microsoft Fabric Data Warehouse
50mAzure SQL DB Data Portability : Mirroring, CDC, Export/Import and DataSync
47mData analytics for the era of AI
19mAccelerate your data potential with Fabric
27mModernize your data integration to enable petabyte scale analytics with Microsoft Fabric
30mDataEngBytes 2023 - BRI-T1-04 - Mimoune Djouallah
