windows failover cluster

When Read-Scale availability groups and Windows Failover Cluster are not good friends

A couple of days ago, with some fellow French data platform MVPS (@thesqlgrrrl and @Conseilit) we discussed an issue around Read-Scale availability groups(…)

Dealing with WSFC 2016 quarantine state and availability groups

I was playing with my lab environment which includes Windows 2016 and SQL Server 2016 and I noticed an interesting scenario while testing cluster node failures. After simulating some network outage scenarios, I was not able to(…)

Migrating your existing availability group infrastructure to 2016

Have you already a plan to migrate your old SQL Server 2012 availability group infrastructure to windows 2016 and SQL Server 2016? In a previous post, I talked about distributed availability groups and cross-cluster migration scenarios(…)

Windows Failover Cluster : Introduction to paxos tag

A couple of days ago, I was in charge to install a new SQL Server AlwaysOn and availability group with one of my colleague Nathan Courtine. During the installation, we talked about testing a disaster recovery(…)

Windows Server 2016: Introducing stretch cluster functionality

Let’s continue with the new high available functionality shipped with the next Windows version. In my previous blog, I talked about the new site awareness feature that provides more flexibility to configure failover resources priorities and(…)

SQL Server AlwaysOn: when a listener becomes the cluster and vice versa

Let’s talk about a funny story that concerns an interesting issue that I faced a couple of months ago at one of my customers. Initially, the problem concerned only the creation of an availability group listener but after deleting the(…)