Monitor SQL 2025 Fabric mirroring via Fabric Portal, DMVs, and OneLake files to ensure reliable data replication. By Meagan Longoria.
The article explains monitoring SQL Server 2025 Fabric mirroring using the Fabric Portal (table-level metrics), SQL Server DMVs like sys.dm_change_feed_log_scan_sessions, and OneLake files. It emphasizes tracking replication status, delays, errors, and log usage to maintain data consistency.
Key points in the blog post:
- Use Fabric Portal for quick status checks and delay metrics.
- Monitor
sys.dm_change_feed_log_scan_sessionsfor session health and stalled phases. - Check
sys.dm_change_feed_errorsfor persistent replication issues. - Validate OneLake files (
tables.json,Manifest_1.json) for data integrity. - Schema changes may inflate
schema_change_countdue to multiple log records. - Log truncation delays require balancing mirroring performance with log size limits.
- Extended Events provide deep troubleshooting but should be used sparingly.
This article provides actionable monitoring strategies for SQL 2025 Fabric mirroring, bridging SQL Server and Fabric ecosystems. While incremental (e.g., new file structures), it’s critical for ensuring replication reliability. It advances troubleshooting by tying SQL-side metrics to OneLake artifacts, though schema change tracking nuances may require deeper analysis. Good read!
[Read More]