Automatic seeding of availability database failed with an unrecoverable error: it showed on the secondary, then vanished. Here is what ERRORLOG said.
SQL SERVER – T-SQL Script to List Automatic Seeding of Always On Availability Group
Automatic seeding for Always On availability groups came in SQL Server 2016. Here is the T-SQL script we used in a Health Check to list databases and their seeding.
SQL SERVER – Drop failed for Availability Group – Failed to Destroy the Windows Server Failover Clustering Group Corresponding to Availability Group
While recovering a cluster in ForceQuorum mode, dropping an availability group failed: Failed to destroy the WSFC group. Here is how I got past this error.
SQL SERVER – Error: 9642 – An error occurred in a Service Broker/Database Mirroring transport connection endpoint
Error 9642 in the ERRORLOG: an error occurred in a Service Broker/Database Mirroring transport connection endpoint. Here is what caused it for my client.
SQL SERVER – Error in Validation: Listener in Workgroup – Unable to determine if the computer exists in the domain ‘WORKGROUP’
A client’s domain-less Always On cluster in Azure could not create a listener: Unable to determine if the computer exists in the domain ‘WORKGROUP’. Here is why.
SQL SERVER – Read Only Routing Error: Client Unable to Establish Connection Because an Error was Encountered During Handshakes Before Login
A client’s Always On read-only routing failed with: an error was encountered during handshakes before login. Here are the checks I shared and how we fixed it.
SQL SERVER – Availability Group Seen in SSMS but missing in Cluster Manager. What’s Wrong?
A client’s availability group showed in SSMS, but no role appeared in Failover Cluster Manager. Here is the sequence of steps that causes this and what to do.