Forum Discussion
Moving Mirrored SQL database between workspace
Hi pmscorca ,
Thank you for reaching out to the Microsoft Community Forum.
You can’t “move” a mirrored SQL database from one workspace to another using a “move” command or drag‑and‑drop.
Please try below alternative workaround steps.
1. Recreate the Mirrored Database in the Target Workspace: Switch to the target workspace where you want the mirrored database.
Click Create --> See more --> Mirrored SQL database.
configure your existing SQL Server connection . Name and configure the database, then click Mirror database. This starts replicating data into a new OneLake location in that workspace via Delta/Parquet.Note: The mirrored database is read-only via its SQL analytics endpoint and exists entirely within the target workspace.
2. In the old workspace, locate the mirrored DB under Data Warehouse. Use the Delete option to remove it and free up resources this does not affect the original SQL source.
Note: If you want to transfer only the mirrored data not the mirroring setup between workspaces:Use fabric pipelines to copy tables across workspaces. Source: Lakehouse in old workspace. Sink: Lakehouse in target workspace. Configure either via the UI OneLake catalog or by specifying workspace/lakehouse IDs via dynamic parameters.
Please refer below links.
Microsoft Fabric Mirrored Databases From SQL Server - Microsoft Fabric | Microsoft Learn
Copy data across workspaces - Microsoft Fabric | Microsoft Learn
I hope this information helps. Please do let us know if you have any further queries.
Regards,
Dinesh
Hi, ok but do I need to accomplish any operations on the SQL Server source on-premise for recreating the mirrored SQL database in the target workspace? Thanks
Hi pmscorca ,
You need to do few operations on your on‑premises SQL Server source before Fabric can create and keep the mirror in sync.
Please try below operations from on‑prem SQL Server.
1. Install and register an On‑Premises Data Gateway in the same network as SQL Server. Fabric uses the gateway to securely connect to your on‑prem server. The gateway must show Online in Fabric tenant settings and be selectable when you create the mirror.
2. Allow the gateway machine to reach the SQL Server (default TCP 1433 or named instance port) and allow outbound connectivity from gateway to Microsoft Fabric endpoints. If SQL Server isn’t publicly reachable, the gateway is the supported path. (VNet data gateway is not currently supported for some on‑prem mirroring.)
3. Fabric connects using a least‑privilege login. For SQL Server 2016–2022, grant SELECT on the mirrored tables plus the permissions required by the mirroring service. SQL Server 2025 adds new permissions for “external mirror”.
4. Enable Change Data Capture (CDC) on the source database and tables for SQL Server 2016–2022. Fabric mirroring relies on CDC to produce the continuous change feed. Enable at database level and for each table you plan to mirror. Also ensure SQL Server Agent is running CDC jobs depend on it.
Note: For SQL Server 2025, Fabric uses a different mechanism, CDC is not supported for mirroring on that version; follow the 2025‑specific permissions and limitations. Supported sources like SQL Server 2016–2022 (Windows) and SQL Server 2017 Linux (with CU18+). There are platform and feature limitations like number of tables, AG/FCI constraints, so review before enabling.
Please refer below links.
Tutorial: Configure Microsoft Fabric Mirroring from SQL Server - Microsoft Fabric | Microsoft Learn
Limitations of Fabric Mirrored Databases From SQL Server - Microsoft Fabric | Microsoft Learn
I hope this information helps. Please do let us know if you have any further queries.
Regards,
Dinesh
Hi pmscorca ,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.
Regards,
Dinesh