My client’s AG listener worked fine in Failover Cluster Manager, yet SSMS showed nothing. Here is what causes a listener missing in SSMS and the fix.
SQL SERVER – FIX: Msg 41105: Failed to Create the Windows Server Failover Clustering (WSFC) Resource With Name and Type ‘SQL Server Availability Group’
Creating an availability group failed with Msg 41105: Failed to create the WSFC resource with type ‘SQL Server Availability Group’. Here are ways to fix it.
SQL SERVER – AlwaysOn – Queries Waiting for HADR_AR_CRITICAL_SECTION_ENTRY
After a Windows cluster briefly lost quorum, a client’s AlwaysOn queries got stuck waiting for HADR_AR_CRITICAL_SECTION_ENTRY. Here is how we fixed the wait.
SQL SERVER – Cluster Resource ‘AGName’ of type ‘SQL Server Availability Group’ in Clustered Role ‘AGName’ Failed
Configuring an availability group is easy; trouble starts when the cluster breaks. Here I fix a failed cluster resource of type SQL Server Availability Group.
Full-Text Index Blocking Redo on an Always On Secondary
A full-text index can block the redo thread of a readable Always On secondary. This post shows the three clues to read in sys.dm_exec_requests, how to find the internal table and how to check change tracking. It ends with the fix: manual tracking and a scheduled population.
SQL SERVER – Unable to Create Always On Listener – Attempt to Locate a Writeable Domain Controller (in Domain Unspecified Domain) Failed
Can’t create an Always On listener? On three clusters, Event ID 1212 said the attempt to locate a writeable domain controller failed. I walk you through the fix.
SQL SERVER – Always On Secondary Replica Huge Redo Queue – Version Store is Full. New Version(s) Could Not be Added
The redo queue kept growing on an Always On secondary replica, and the ERRORLOG said version store is full. Here is what I found and why it happened.