2026-02-09
493 reads
2026-02-09
493 reads
This guide helps you get started on troubleshooting some of the common issues in AlwaysOn Availability Groups and monitoring AlwaysOn Availability Groups. It is intended to provide original content as well as a landing page of useful information that is already published elsewhere.
2024-01-09 (first published: 2021-08-25)
Availability databases hosted on SQL Server Always On Availability Groups (AG) can be connected using a unique Virtual Network Name (VNN), called the Availability Group Listener. When an Availability Group is enabled, clients can connect to databases in both primary and secondary replicas without explicitly specifying the SQL Server instance name. You don’t even need […]
2021-05-17
10,107 reads
Availability databases hosted on SQL Server Always On Availability Groups (AG) can be connected using a unique Virtual Network Name (VNN), called the Availability Group Listener. When an Availability Group is enabled, clients can connect to databases in both primary and secondary replicas without explicitly specifying the SQL Server instance name. You don’t even need […]
2019-07-02
138,163 reads
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
By HeyMo0sh
As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...
Hi everyone I asked this earlier but the desired outcome is a bit different...
Hi, I have a SQL Server instance where users connect to via Windows Authentication,...
Comments posted to this topic are about the item Multiple Deployment Processes
I have a query from a former DBA that we run on SQL Server 2025 to check on database metadata. This query references sys.sysaltfiles. I want to refactor this code to be more modern. Which DMV should I reference instead?
See possible answers