Skip to content

Latest commit

 

History

History
32 lines (21 loc) · 1.51 KB

known-issue-723-sql-azure-database-change-data-not-propagate-mirror.md

File metadata and controls

32 lines (21 loc) · 1.51 KB
Raw
title description author ms.author ms.topic ms.date ms.custom
Known issue - Azure SQL Database change data doesn't propagate to mirror
A known issue is posted where Azure SQL Database change data doesn't propagate to mirror.
mihart
jessicamo
troubleshooting
05/24/2024
known-issue-723

Known issue - Azure SQL Database change data doesn't propagate to mirror

If you set up Fabric mirrored databases from Azure SQL Database, you might see that some of the change data might not propagate to the mirror. The issue occurs when the SQL database mirror is actively replicating source operational data and the service level objective (SLO) is changed. Specifically, if you change the SLO by either:

  • Azure SQL database SLO is upgraded in the following sequence: Update SLO to Standard/Business Critical/General Purpose and then upgrade to Hyperscale
  • Azure SQL database SLO is reverse migrated from Hyperscale to Standard/General Purpose/Business Critical SLO

Status: Open

Product Experience: Data Warehouse

Symptoms

Change data from Azure SQL Database isn't propagated to the Fabric mirrored database. If you query the logs, you see errors similar to dwError 32 SQLError.

Solutions and workarounds

You can try to restart the data propagation by starting and stopping the mirror. If restarting doesn't fix the issue, contact Microsoft support.

Related content