Data Monitoring / SQL Server Availability & Capacity
SQL Server: Monitoring permission changes
A collector returns fewer rows after a database upgrade. Compare collector errors, documented DMV permissions and the effective monitoring identity.
Environment and inputs: SQL Server operational monitoring; availability groups, SQL Agent and host-level metrics depend on edition, service and deployment.
Failure scenario
A collector returns fewer rows after a database upgrade. Confirm the cause before choosing a fix.
Evidence to collect
Compare collector errors, documented DMV permissions and the effective monitoring identity. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Grant the minimum version-appropriate permissions and verify coverage rather than interpreting empty results as healthy. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for monitoring permission changes 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.