<aside> 🧭

Navigation:

• Architecture & AI & Documents Indexers
• Architecture & Monitoring : Measuring Performance issues of Dynamics 365 with Dynatrace and StresStimulus
• Architecture & Integration : Power Platform & SAP
• Resiliency & Architecture for integration service between Power Platform and SAP
• Resiliency for Autonomous Service (Power BI & Power Platform)
• Microsoft 365 Copilot Early Access Program
• Migration/Synchronization Plan from SQL Server On-Premise to Microsoft Fabric

</aside>

Purpose

Design the migration architecture and the synchronisation architecture in order to create an action plan including the type of interventions et the actors involved in the process.

Context

We want to design an architecture using Fabric and 4 on-premises SQL Servers (dev, QA, pre-production & production). we need to create an architecture that uses Fabric both for migrating data to Fabric and for integrating both Fabric and my SQL Server instances, as we must keep these SQL Servers.

What architecture do we suggest? Please note, We prefer to follow the Mesh architecture and the bronze, silver, and gold data concept, before presenting it in a Power BI report.

Starting points with constraints

• The SQL Server databases hold 1 TB of data (max).
• We are ready to upgrade the SQL Server version to 2022.
• We are already using the Always On technology for SQL.
• Data transformation is required.
• For transformation, we want to consider both approaches: no-code/low-code and code-based (Python) using Spark and notebooks. We want both scenarios.
• We are already using Power BI and are experiencing performance issues during refreshes (semantic model).
• We want report refreshes (semantic model) to occur in under 5 minutes.
• We want user interaction with data display to be under 5 seconds.
• We want the data to be near real-time.
• No matter what, the performance has to be taken into account.