SQL Server AlwaysOn Availability Groups

SQL Server Always on Availability Related Queries:

How do I switch Primary / Secondary on Switch Always on Availability Groups ( Swap Primary / Secondary ):
When the automatic failover is setup , the Primary / Secondary gets swapped during maintenance tasks.
To swap back the Primary/Secondary , connect to the server which’s secondary and run the following command. If you run it on the principal node, you will encounter the following error.

Always-On Replica Cluster Status:

Remove Database from AlwaysOn Availability Group and Set Database OFFLINE

Failover is Not Immediate. WSFC failover is pretty impressive—it usually happens in a matter of 2-3 seconds or less (where there are ‘clean’ failures). Still, once a SQL Server instance spins up somewhere and takes control of database resources, it’s going to have to walk through the recovery process. With Availability Group Replicas, this recovery time is typically going to be brief (when we’re talking about synchronous replicas)—where brief can be on the order of 20-40 seconds. With Failover Cluster Instances, however, the new active node is basically starting from scratch—a cold-start as it were—and typically takes a bit under a minute to be ready to start serving all databases as needed. For more info, check out my post on indirect checkpoint—a VERY cool (but powerful) feature of SQL Server 2012.


Alwayson Throughput and Performance Related Issues:
AlwaysOn Performance Related Issues

Monitor Alwayson Availability Groups:
Monitor Alwayson Availability Groups

ALWAYS ON Availability Groups:

Monitor Performance for AlwaysOn Availability Groups

Always On–When Is My Secondary Failover Ready?

SQL Server 2012 AlwaysOn – What is it?

SQL Server AlwaysOn Availability Groups Cheat Sheet

SQL Server AlwaysOn Availability Groups Gotchas

Powershell Script TO Enable:



Handling MetaData


Synchronizing Logins


Leave a Reply

Your email address will not be published. Required fields are marked *