Contents
- 1 Why is my availability database in an unhealthy synchronization state?
- 2 Is the data synchronization state of SQL Server not healthy?
- 3 Why is my AlwaysOn database in an unhealthy state?
- 4 Why is Availability mode not set to synchronous?
- 5 Can a readable secondary replica be in synchronous commit mode?
Why is my availability database in an unhealthy synchronization state?
Error: At least one availability database on the replica has an unhealthy data synchronization state. If this is an asynchronous-commit availability replica, all availability databases should be in the SYNCHRONIZING state.
Is the data synchronization state of SQL Server not healthy?
SQL Server: Data synchronization state of some availability database is not healthy. Data synchronization state of some availability database is not healthy. This policy checks the data synchronization state of the database replica.
Is there an unhealthy data synchronization state on a replica?
At least one availability database on the replica has an unhealthy data synchronization state. If this is an asynchronous-commit availability replica, all availability databases should be in the SYNCHRONIZING state.
Why is my AlwaysOn database in an unhealthy state?
AlwaysON – SYNCHRONIZING state – Data synchronization state of some availability database is not healthy. The problem: One of the AlwaysON replicas is in an unhealthy state when the data synchronization state is in SYNCHRONIZING state for the synchronous-commit database replica.
Why is Availability mode not set to synchronous?
Availability Mode is set to Synchronous commit and when I reboot the secondary node some DBs (randomly) get in a “Not Synchronized” state and they can’t go back to “Synchronized”. Everything looks OK, I have another SQL installation with same patching level and Os and it’s working fine.
When is an AlwaysOn replica in an unhealthy state?
One of the AlwaysON replicas is in an unhealthy state when the data synchronization state is in SYNCHRONIZING state for the synchronous-commit database replica. Error: At least one availability database on the replica has an unhealthy data synchronization state.
Can a readable secondary replica be in synchronous commit mode?
A readable secondary replica can be in either synchronous-commit availability mode, or asynchronous-commit availability mode. A readable secondary replica allows read-only access to all its secondary databases. However, readable secondary databases are not set to read-only. They are dynamic.