A client’s availability group failover across subnets got stuck in Resolving and generated dumps with Error 17066. Here is what we found and how we fixed it.
SQL SERVER – Always On Availability Group Error 35250: The Connection to the Primary Replica is Not Active
Joining a database to an availability group can fail with Availability Group Error 35250. Here is why it shows up in the wizard and how I fix it.
SQL SERVER – AlwaysOn Availability Group Backup fn_hadr_backup_is_preferred_replica Not Working Correctly
A client’s backups to the secondary never ran because fn_hadr_backup_is_preferred_replica returned 0 on every node. Here is what I found in its code.
SQL SERVER – AlwaysOn Wizard Error – Checking for Compatibility of the Database File Locations on the Server Instance that Hosts Secondary Replica
The AlwaysOn wizard failed while checking database file locations on the secondary replica, though the drives were correct. Here is the workaround.
SQL SERVER – AlwaysOn Wizard Error – The Endpoints Tab Lists at Least One Endpoint that Uses Only Windows Authentication
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.