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 […]

Contained Availability Groups

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.

Always On Availability Groups Troubleshooting and Monitoring Guide

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.

A Step by Step Guide to the Availability Group (AG) Listener

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 […]

Basic Availability Groups

Do *not* place TEMPDB on a local disk in a SQL failover cluster

What happens with tempdb on a local disk in a cluster? Read on to see that you will not get a failover if the local disk fails