Fabric SQL Server Managed Instance Mirroring

Hi fabricpribeiro,

Thankyou for the followup.

Based on my understanding, SQL Server MI mirroring to Microsoft Fabric is a managed, read-only analytical replication service that maintains only the current state and does not expose CDC or ingestion metadata at the table or row level.

Regarding Append versus Merge:

1. Fabric mirroring applies changes with semantics similar to MERGE. The Fabric warehouse always reflects the latest state of the source tables, no history is retained. A record inserted at source will appear in Fabric, and a record later deleted at source will be removed from Fabric. There is no SCD Type 2 behaviour and no historical versions.

Regarding metadata, ingestion time, and sync status:

1. Fabric mirroring does not add ingestion timestamps or CDC metadata to tables. It does not expose rows inserted, updated, or deleted, nor does it provide per table sync success or failure information.

Please consider the following approach to manage metadata:

1. It is not possible to request that the mirroring process populate a metadata table. Instead, create a downstream monitoring solution (for example, a separate Warehouse or Lakehouse) and periodically capture table existence, row counts, and observation timestamps. Store these in a custom metadata table for operational tracking. For row level history or auditing, enable CDC at source or use Fabric Data Pipelines / Dataflows Gen2 downstream. Mirroring alone is not designed for historical tracking.

We hope this information helps to resolve the issue. If you have any further queries, please feel free to contact the Microsoft Fabric community.

Thank you.