The Secondary Database Name in an AG

Basic Always On Availability Groups in SQL Server Standard

Once Windows Server Failover Clusters have been set up, we can set up Availability Groups in SQL Server. This article will focus on setting up Basic Always-On Availability Groups in SQL Server Standard Edition.
This facilitates High Availability in SQL Server Standard, with three levels of availability and failover:
Asynchronous commit with manual or forced failover,
Synchronous commit with manual or forced failover,
Synchronous commit with automatic failover.

Troubleshoot SQL Server Always On Availability Groups with SQL LogScout

We experienced several unplanned outages and failovers on our SQL Server Always On Availability Groups. We want to know the root cause to prevent them from happening in the future. How do we identify the root causes of unplanned Availability Group outages and failovers?

Read Only Replica in SQL Server Standard

SQL Server Standard Always On Availability Groups

Always On Setup

Contained AG MSDB Naming

Contained AG Databases

Add a Second NIC for an Availability Group to Separate Network Traffic

Introduction Sometimes we face the scenario in an enterprise environment that the database in SQL Server Always On Availability Group (AOAG) has high concurrency read and write access from application servers. If we keep using the one network interface card for both network traffic of database connections from application servers and database mirroring between AOAG […]

How to Use PowerShell to Track a Network Latency Issue in an Always On Availability Group

This article tracks down a problem with Availability Groups due to network bandwidth.