Data Monitoring / SQL Server Availability & Capacity
SQL Server: Replica read freshness
A read-only dashboard returns older data than the primary. Compare routing destination, replica synchronization evidence and the business watermark.
Environment and inputs: SQL Server operational monitoring; availability groups, SQL Agent and host-level metrics depend on edition, service and deployment.
Failure scenario
A read-only dashboard returns older data than the primary. Confirm the cause before choosing a fix.
Evidence to collect
Compare routing destination, replica synchronization evidence and the business watermark. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Route freshness-critical reads appropriately or disclose the measured lag to users. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for replica read freshness using the same scope and a representative interval. Check that the symptom is resolved, expected records are present and downstream results are correct. If coverage, correctness or latency worsens, restore the recorded configuration through the agreed rollback process.
Scope and precautions
Prefer read-only access and limit queries to the relevant period or dataset. This example has not been tested on your systems. Test changes in an approved environment. Keep credentials and sensitive data out of shared evidence.