Forum Discussion
Connecting to a mirrored SQL Server database source in a copy activity
Hi pmscorca,
Thank you for reaching out to Microsoft Fabric Community.
Thank you apturlov for the prompt response.
Currently this is a fabric limitation by design. Since this capability is not supported so I recommend upvoting the idea you created so the product team can track and consider it for future support. For now the current behaviour and workarounds remain the supported approach.
Thanks and regards,
Anjan Kumar Chippa
pmscorca I am puzzled with the context change. Not sure how your original question relates to your idea about a dataflow. But, yes, the mirrored SQL database (does not matter whether Azure or on-prem) cannot be used as a data source in Dataflow Gen2 as well. I would think the rationale is the same as in data pipelines: the data is already here, no need to duplicate. Now, there is a workaround for both scenarios: you can create shortcuts for mirrored tables in a Lakehouse, then use the Lakehouse as a data source and the shortcut tables will be visible in the list of tables:
This technique also applies to practically any workload that works with a Lakehouse.
If you find this answer useful or solving your problem please consider giving kudos and/or marking as a solution.
Hi, thanks for your reply.
I prefer to refer a mirrored database in a warehouse by a specifying a fully qualified table (catalog_name.schema_name.table_name) in a query respect to create a shortcut in a lakehouse.
I think that a mirroring database could be at bronze level as for a lakehouse: it could be necessary apply some data transformations from bronze to silver/gold level, and therefore from a lakehouse or mirrored database to a warehouse; also for a lakehouse the related data could be duplicated in the next warehouse after applying some data transformations.
Hi pmscorca,
Thank you for reaching out to Microsoft Fabric Community.
Thank you apturlov for the prompt response.
Currently this is a fabric limitation by design. Since this capability is not supported so I recommend upvoting the idea you created so the product team can track and consider it for future support. For now the current behaviour and workarounds remain the supported approach.
Thanks and regards,
Anjan Kumar Chippa