How to Mirror a Fabric SQL Database (Not Azure SQL) and Access the Mirrored Data

[bhavya5903]

Hi everyone,

I'm working with Microsoft Fabric and trying to set up mirroring for a Fabric SQL Database (NOT Azure SQL Database or any other type of mirroring). I want to understand the following:

1. How do I set up mirroring specifically for a Fabric SQL Database?
2. Once mirrored, how can I access the mirrored data — for example, through the SQL Analytics Endpoint or directly from OneLake (e.g., as a Parquet file)?
3. Are there any best practices or potential issues to watch out for when setting this up?

[v-karpurapud]

Hi @bhavya5903 

I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please Accept it as a solution and give it a 'Kudos' so others can find it easily.

Thank you.

[v-karpurapud]

Hi @bhavya5903 

Hope you are doing well!

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you.

[v-karpurapud]

Hello @bhavya5903 

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[v-karpurapud · Accepted solution]

Hello @bhavya5903 

Thank you for reaching out to the Microsoft Community Forum.

We understand that you are seeking insights on setting up mirroring for a Fabric SQL Database.Here is the detail information that might helpful for you:

1. Create the SQL Database in Microsoft Fabric:

When you create a SQL database in Microsoft Fabric, it automatically provisions the SQL database, SQL analytics endpoint, and default semantic model in your workspace. Mirroring starts automatically with all supported tables and columns mirrored upon creation, requiring no additional settings.

2. Accessing Mirrored Data:

SQL Analytics Endpoint:

• The mirrored data is stored as Delta Parquet files in OneLake. The SQL analytics endpoint points to these files, allowing you to query the mirrored data using familiar T-SQL commands. The data accessed via the SQL analytics endpoint is read-only, protecting the operational data source from accidental writes or deletes.
  
  

Direct Access from OneLake:

• The mirrored data in OneLake can be accessed directly as Parquet files, enabling downstream scenarios like data engineering, data science, and more.

3. Best Practices and Potential Issues:

Data Consistency:

• Regularly monitor the mirroring process to ensure data consistency between the primary and mirrored databases, and promptly resolve any discrepancies.
  
  

Performance Monitoring:

• Continuously monitor the performance of both the primary and mirrored databases to ensure the mirroring process does not adversely affect the primary database's performance.
  

Security and Permissions:

• Carefully manage permissions to ensure only authorized users have access to the mirrored data, and follow best practices for securing your data in OneLake and the SQL analytics endpoint.

For more details, you can review Microsoft’s official document:

Overview of Mirroring for SQL database (preview) - Microsoft Fabric | Microsoft Learn

Limitations of Mirroring for SQL database (preview) - Microsoft Fabric | Microsoft Learn
 

If my response has resolved your query, please mark it as the Accepted Solution to assist others. Additionally, a 'Kudos' would be appreciated if you found my response helpful.

Thank you!

[NandanHegde]

Not sure, what your ask is here?
Mirroring is a concpet to bring in data from other sources within Fabric ecosystem. Fabric SQL database is already a part of Fabric ecosystem.

So what do you mean by mirror a fabric SQL database?
Do you want to copy data from 1 fabric SQL database into another?