Setting up an availability group, a client hit an AlwaysOn Wizard Error: an endpoint uses only Windows Authentication. Here is why and how we got past it.
SQL SERVER – Error – Auto Close is Enabled. Only Databases with Auto Close Disabled can be Added to an Availability Group
The AlwaysOn wizard said auto close is enabled, so the database can’t join an availability group. Here is why, and the settings to change first.
SQL SERVER – Adding New Database to AlwaysOn Replica is Slow
A client with five replicas said adding a new database to their AlwaysOn Replica setup was slow. Here is what we found while the issue was happening.
SQL SERVER – Caution: Adding Node in AlwaysOn Availability Group
Three clients hit the same issue after adding node at a DR site to an AlwaysOn cluster: disks on the original servers went offline. Here is what to watch for.
SQL SERVER – FIX: Msg 35250 – The Connection to the Primary Replica is Not Active. The Command Cannot be Processed
A reader still got Msg 35250 after my first post, with no mirroring login error in the ERRORLOG. Here are the endpoint and service account checks I asked for.
SQL SERVER – AlwaysOn Join Error – Msg 1408, Level 16 – The Remote Copy of Database “SQLAUTH” is Not Recovered Far Enough to Enable Database Mirroring or to Join it to the Availability Group
I do provide consultancy services for deployments, including AlwaysOn availability group deployments. AlwaysOn Join Error.
SQL SERVER – FIX: Msg 35250, Level 16, State 7 – The Connection to the Primary Replica is Not Active. The Command Cannot be Processed
Joining a database to an availability group failed with Msg 35250: the connection to the Primary Replica is not active. Here is why and how to fix it.