Hey everyone, it's Will here. I hope you are having a wonderful week! Just wanted to share some exciting updates from our second community Fabric Dojo - we are just about to start building a Real-World Fabric Solution, over a 10-week period. So if anyone is looking to gain real-world experience with Fabric (to help you get/ excel in a job) - then this will be a great opportunity for you! This project is designed to simulate the type of Fabric solution you would build within a real enterprise environment. You will be challenged to think, design, and deliver like a professional Fabric Data Engineer — from strategy through to implementation. By the end of this project, you will: - Understand how all engineering components of Microsoft Fabric interact as part of a coherent, end-to-end data platform - Develop the ability to move from business outcomes and client requirements, through solution architecture design, and into the build and delivery phase - Experience a realistic project lifecycle, including iteration, validation, refinement, and presentation Here's the schedule for the next 10 weeks or so: - Project Kick-off (15 Oct - but you can catch the recording): Introduction to the real-world client, project context, and goals - Sprint 1 (20–27 Oct): Capacity & Workspace Design - Define Fabric capacities and workspace strategy based on client needs - Sprint 2 (27 Oct – 3 Nov): CI/CD & Automation - Establish GitHub repository & develop CI/CD & Automation strategy, based on the client requirements. - Sprint 3 (3–10 Nov): Data Architecture & Data Stores - Design data architecture and implement Fabric data stores - Sprint 4 (10–17 Nov): Data Extraction - Build ingestion pipelines from client source systems (in some instances, synthetic data will be provided to protect sensitive data) - Sprint 5 (17–24 Nov): Data Transformation - Design a scalable transformation framework across architectural layers - Sprint 6 (24 Nov – 1 Dec): Data Validation & Quality - Implement data validation framework and centralised DQ monitoring - Sprint 7 (1–8 Dec): Orchestration - Build orchestration layer to integrate extraction, transformation, and validation processes - Sprint 8 (8–15 Dec): Logging & Alerting - Implement operational logging and alerting across the platform - Extension Sprint 9 (15 Dec – 5 Jan): Further Development - For those that want to push their skills even further, I'll be providing a number of extension tasks to be completed over the Christmas period. These will include: developing a end-to-end testing framework & developing Infrastructure-as-Code templates to support future platform evolution. - Project Showcase & Closeout (5 Jan): Present your final solution to “the client” (the community and Will) & Celebration and next steps discussion

Hi all, I have a client that is currently using databricks and power bi. They have multiple clusters of databricks running and want to consolidate into one analytics platform. I've suggested Fabric, what would be the reasons for migrating over to fabric instead of using databricks? or would a hybrid approach be better, by using fabric and databricks? Will Fabric be cheaper to run as one platform? Please let me now your thoughts.

Hey all, I took the DP-700 today and passed! I will write a proper post with my experiences when I get home later today, but I’ll say it’s definitely a thorough test of your skills! Look forward to now switching to thinking about how best to teach the content to all of you! 🙌🏽

I'm looking into getting on-prem SQL tables into Fabric. We're looking at mirroring but that currently seems to rely on a sort of workaround using replication to Azure SQL before mirroring: Mirroring SQL Server database to Fabric | Microsoft Fabric Blog | Microsoft Fabric as Will posted here: Mirroring for on-prem SQL Server · Learn Microsoft Fabric. Given there is now SQL directly in Fabric: Announcing SQL database in Microsoft Fabric (Preview) | Microsoft Fabric Blog | Microsoft Fabric. Can you not set up replication for the on-prem SQL Server directly to SQL in Fabric? Has anyone tried it? I currently am trying it but hitting a roadblock because our SQL Server is pre-2022 and doesn't support Entra Authentication. I'm wondering whether it is worth pushing the relevant team to upgrade but don't want to if it won't work anyway.

Hi there all, Happy New Year! I've reviewed documentation here: Limitations and Behaviors for Fabric Mirrored Databases From Azure SQL Database - Microsoft Fabric | Microsoft Learn and here: Limitations for SQL database (preview) - Microsoft Fabric | Microsoft Learn I'm under the impression that: - Table Names are now supported with spaces: Fabric September 2024 Monthly Update | Microsoft Fabric Blog | Microsoft Fabric and thus, mirroring with Tables with spaces should work too. - Column Names with spaces or other special characters is still not supported and thus, mirroring Tables with such columns will not work. Do I have that right? I don't know if there is any desire from Microsoft to try and accommodate them? does anyone know about any workaround to allow mirroring of a DB that does have special characters/spaces in column names?