SQL Server Mirroring - how to identify latest replicated records

Hi krisjones 

SQL Server Mirroring helps keep databases synchronized for high availability, but it doesn’t provide the same row-level change tracking that Delta Lake’s Change Data Feed (CDF) offers in Fabric. Mirroring is designed mainly for disaster recovery and ensures both databases stay identical, but it doesn’t store information about what data was changed, updated, or inserted. That’s why Fabric can’t enable CDF on mirrored tables , it has no change metadata to work with. If your goal is to track incremental updates, you can use SQL Change Tracking (CT) or Change Data Capture (CDC) instead, as both are made for identifying new or modified records. You can enable CT or CDC on your source SQL database before mirroring and then use that data in your ETL or Fabric pipelines. This setup allows you to capture only the changes without stressing the mirrored database. In short, mirroring keeps data in sync but not aware of changes, so CT or CDC is the best way to achieve incremental refresh similar to CDF.