SQL Server Always On

Start Here

Manual Home Installation Getting Started Licensing Servers Connect Database Servers Troubleshoot Connectivity Host OS Login Enable WMI Multi-Engine Settings

Console

Console Overview Enterprise View AI Assistant Execution Plans Alerts Custom Alerts Reports Settings Service Log Connectivity Log Web Log About

PostgreSQL

Overview Connection and Permissions Activity Databases Queries Waits Memory I/O Indexes Deadlocks Server Log Settings Permissions Health Checks Alerts Performance Tuning

MySQL/MariaDB

Overview Connection and Permissions Activity Databases Queries Memory I/O InnoDB Permissions Deadlocks Health Checks Alerts Performance Tuning

Oracle

Overview Connection and Permissions Activity Databases Queries Waits Memory Health Checks Alerts Performance Tuning

Settings And Integrations

Security SQL Options Email Server Alert Recipients Recipient Groups Server Groups Cloud Providers Web Proxy Slack Microsoft Teams PagerDuty Jira Performance Logging AI Provider MCP Server

Legacy Documentation

The SQL Server Always On page shows Availability Group, replica, and database synchronization health. Use it to monitor high availability and disaster recovery status.

What You Can See

Availability groups.
Replica health.
Database synchronization state.
Primary and secondary health.
Group synchronization health.
Database-level availability status.

Workflow

Open Always On for the SQL Server.
Review health badges for groups, replicas, and databases.
Select groups or replicas for detail where available.
Check Error Log for matching availability messages.
Check Alerts for related availability alerts.

How To Review Always On Health

Use the Always On page when availability, failover readiness, or replica synchronization is the question. It helps DBAs see whether availability groups, replicas, and databases are healthy from the monitoring console before drilling into SQL Server error messages or alerts.

Start with unhealthy or warning states, then identify whether the issue affects one database, one replica, or the whole availability group. A database-level synchronization problem may have a different cause from a replica connectivity problem. Compare the page with SQL Server Error Log for failover, seeding, connection, and recovery messages.

For production high availability environments, record the group, replica, database, time, and observed state before making changes. Availability fixes can affect failover behavior and should follow your normal SQL Server HA process.