<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: On-Prem SQL Mirroring in SQL database</title>
    <link>https://community.fabric.microsoft.com/t5/SQL-database/On-Prem-SQL-Mirroring/m-p/4365584#M159</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="782160" data-lia-user-login="Srisakthi" class="lia-mention lia-mention-user"&gt;Srisakthi&lt;/a&gt;&amp;nbsp;- Replication is an option when you need more discrete control of what is being replicated to Fabric.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can also replicate directly to Fabric SQL database. It is actually documented with Azure SQL here:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://learn.microsoft.com/en-us/azure/azure-sql/database/replication-to-sql-database" target="_blank" rel="noopener"&gt;https://learn.microsoft.com/en-us/azure/azure-sql/database/replication-to-sql-database&lt;/A&gt;. 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.&lt;/P&gt;</description>
    <pubDate>Wed, 15 Jan 2025 17:42:50 GMT</pubDate>
    <dc:creator>dlevy</dc:creator>
    <dc:date>2025-01-15T17:42:50Z</dc:date>
    <item>
      <title>On-Prem SQL Mirroring</title>
      <link>https://community.fabric.microsoft.com/t5/SQL-database/On-Prem-SQL-Mirroring/m-p/4364899#M157</link>
      <description>&lt;P&gt;Hello Everyone,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;A href="https://support.fabric.microsoft.com/en-ca/blog/mirroring-sql-server-database-to-fabric?ft=All" target="_blank"&gt;https://support.fabric.microsoft.com/en-ca/blog/mirroring-sql-server-database-to-fabric?ft=All&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The question which came to mind is&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;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?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Srisakthi&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Jan 2025 10:32:08 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/SQL-database/On-Prem-SQL-Mirroring/m-p/4364899#M157</guid>
      <dc:creator>Srisakthi</dc:creator>
      <dc:date>2025-01-15T10:32:08Z</dc:date>
    </item>
    <item>
      <title>Re: On-Prem SQL Mirroring</title>
      <link>https://community.fabric.microsoft.com/t5/SQL-database/On-Prem-SQL-Mirroring/m-p/4365584#M159</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="782160" data-lia-user-login="Srisakthi" class="lia-mention lia-mention-user"&gt;Srisakthi&lt;/a&gt;&amp;nbsp;- Replication is an option when you need more discrete control of what is being replicated to Fabric.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can also replicate directly to Fabric SQL database. It is actually documented with Azure SQL here:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://learn.microsoft.com/en-us/azure/azure-sql/database/replication-to-sql-database" target="_blank" rel="noopener"&gt;https://learn.microsoft.com/en-us/azure/azure-sql/database/replication-to-sql-database&lt;/A&gt;. 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.&lt;/P&gt;</description>
      <pubDate>Wed, 15 Jan 2025 17:42:50 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/SQL-database/On-Prem-SQL-Mirroring/m-p/4365584#M159</guid>
      <dc:creator>dlevy</dc:creator>
      <dc:date>2025-01-15T17:42:50Z</dc:date>
    </item>
  </channel>
</rss>

