Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreWe've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
Hello Everyone,
I have a requirement to mirror on-prem sql db to Fabric. There is a documentation which detailed out on how to achieve this scenario.
https://support.fabric.microsoft.com/en-ca/blog/mirroring-sql-server-database-to-fabric?ft=All
The question which came to mind is
As per the above article it says us to do transactional repliacte to Azure SQL. Why cant we replicate to Fabric SQL Database instead of Azure SQL Database? In that case we can directly use Fabric SQL database right?
Regards,
Srisakthi
Solved! Go to Solution.
Hi @Srisakthi - Replication is an option when you need more discrete control of what is being replicated to Fabric.
For that article, the goal was to get an entire on-prem database mirrored into OneLake. We are working on a way to mirror directly from on-prem databases to OneLake. If this is your scenario, send me a direct message and I can pull the mirroring PM into the conversation to talk about preview opportunities. Azure SQL Database is a good choice there because it can support up to 100TB of space and can be optimized cost-wise to run full time.
You can also replicate directly to Fabric SQL database. It is actually documented with Azure SQL here:
https://learn.microsoft.com/en-us/azure/azure-sql/database/replication-to-sql-database. Replicating directly to Fabric SQL database is a great option if you want to keep your data in a relational format. This option is more costly than just going to OneLake but there are optimizations that can help with that, like optimizing your replication schedule to maximize the time your database stays paused.
Hi @Srisakthi - Replication is an option when you need more discrete control of what is being replicated to Fabric.
For that article, the goal was to get an entire on-prem database mirrored into OneLake. We are working on a way to mirror directly from on-prem databases to OneLake. If this is your scenario, send me a direct message and I can pull the mirroring PM into the conversation to talk about preview opportunities. Azure SQL Database is a good choice there because it can support up to 100TB of space and can be optimized cost-wise to run full time.
You can also replicate directly to Fabric SQL database. It is actually documented with Azure SQL here:
https://learn.microsoft.com/en-us/azure/azure-sql/database/replication-to-sql-database. Replicating directly to Fabric SQL database is a great option if you want to keep your data in a relational format. This option is more costly than just going to OneLake but there are optimizations that can help with that, like optimizing your replication schedule to maximize the time your database stays paused.
Experience the highlights from FabCon & SQLCon, available live and on-demand starting April 14th.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.