Data Monitoring / SQL Server Availability & Capacity
SQL Server: Database availability state
An application loses access while the server process remains running. Compare database state, connection errors and the application's target database.
Environment and inputs: SQL Server operational monitoring; availability groups, SQL Agent and host-level metrics depend on edition, service and deployment.
Failure scenario
An application loses access while the server process remains running. Confirm the cause before choosing a fix.
Evidence to collect
Compare database state, connection errors and the application's target database. Record the time, affected scope and a healthy comparison interval.
Worked diagnostic example
Read-only SQL Server database-state inventory; visibility depends on the monitoring identity.
SELECT name, state_desc, user_access_desc
FROM sys.databases;Fix the confirmed cause
Correct the database-specific cause and verify an authorized application transaction, not merely server uptime. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for database availability state 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.