Knowledge Center

Navigate topics

Always On / High Availability

The High Availability module is built around always on capabilities of SQL server. This module will display all associated always on information for the currently selected server.

The information is displayed by Availability Groups and allows drill down into each group separately.

The Availability Groups will be displayed for the selected server whether it acts as a secondary or primary server in the availability group.

Each Availability Group is comprised of 2 or more servers, one of which is the primary server, which are then comprised of the databases themselves.

Availability Group List Overview

Legend
1 Availability Group List – by default all groups are collapsed. To open an active group use the icon.
2 Active Availability Group – When an Availability Group is Enabled (has no issues) you may collapse or expand on it to view it’s database sync information (see next section: expanded availability group
3 Search + Filters.

Use the filters to focus on a specific group \ database or search for a particular state.

Failover Mode – Automatic \ Manual

Health Status – the health status of the group is comprised of the health status of the underlying databases.

Expanded Availability Group

Legend
1 Status over time – displays the health status changes of the group over the course of the selected timeframe. An empty “status over time” when having a “healthy” availability group is a good indicator.
2 Sync Latency chart – displays gaps in sync latency over the selected timeframe. The closest the chart series are to 0 the better.
3 Database list – the internal database list the comprises the availability group split into servers.

Name Description
Server Name + Role Name of the server and it’s role in the AG. Can be primary or secondary
Failover Mode The failover mode of the server replications. Can be Manual or Automatic
Sync Databases The accumulated value of how many databases are healthy and synced in the server
Details Provides any additional information about the current status
Last Commit Time The last commit time of the database within the syncronization
Redo-Queue Size The redo queue size is the size of transaction logs between its last_received_lsn and last_redone_lsn. last_received_lsn is the log block ID identifying the point up to which all log blocks have been received by the secondary replica that hosts this secondary database.
Latency (MS) The delay that happens between the syncronization process of the databases within the availabilty group.

Request a demo

Fill out your details. 

We’ll get back to you soon.

With Experda, database teams trade manual work with automations and replace clunky operations with streamlined workflows.

Contact Sales

Fill out your details. 

We’ll get back to you soon.

Request a Proposal.

Fill out your details. 

We’ll get back to you soon.

Contact us

Fill out your details. 

We’ll get back to you soon.

Need professional DBA services?

Fill out your details. 

We’ll get back to you soon.

With Experda, database teams trade manual work with automations and replace clunky operations with streamlined workflows.

Need professional BI services?

Fill out your details. 

We’ll get back to you soon.

Get help from Experda

Fill out your details. 

We’ll get back to you soon.

Request a demo

Fill out your details. 

We’ll get back to you soon.

This website uses cookies to remember you and improve your experience. To find out more see our Privacy Policy.