Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AG Setting Change Monitoring #1077

Open
aachaemenes opened this issue Oct 14, 2024 · 2 comments
Open

AG Setting Change Monitoring #1077

aachaemenes opened this issue Oct 14, 2024 · 2 comments

Comments

@aachaemenes
Copy link

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.

@DavidWiseman
Copy link
Collaborator

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.

@aachaemenes
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants