You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DBADash currently tracks changes at database level but when changes happens in AG (changing Sync mode from Sync to Async or another way around) DBADASH wont track them as a change.
These are very important changes that can help with analyzing performance issues. If someone changes AG to Sync from Async and DB size is 10 TB you will have an outage.
The text was updated successfully, but these errors were encountered:
I might look to improve AG monitoring in future versions of DBA Dash & will consider capturing this. If someone changed this it's possible it was done to allow a failover.
you can keep it manual failover with sync or async. if you change it to automatic then yes it will change that to sync by force. There are other settings in AG for backup and routing tables which should be captured when any changes are made.
DBADash currently tracks changes at database level but when changes happens in AG (changing Sync mode from Sync to Async or another way around) DBADASH wont track them as a change.
These are very important changes that can help with analyzing performance issues. If someone changes AG to Sync from Async and DB size is 10 TB you will have an outage.
The text was updated successfully, but these errors were encountered: