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 and Legacy Clustering Preferred Node Check #1027

Open
aachaemenes opened this issue Sep 26, 2024 · 3 comments
Open

AG and Legacy Clustering Preferred Node Check #1027

aachaemenes opened this issue Sep 26, 2024 · 3 comments

Comments

@aachaemenes
Copy link

I think this is a big deal for lots of folks out there to know if their AG or Legacy Clustering is on the preferred node. Thanks.

@DavidWiseman
Copy link
Collaborator

Thanks for the suggestion. I'm not sure if this information is available in the DMVs - if you have a query that captures this, let me know. As a workaround a custom report/collection could be used.

@aachaemenes
Copy link
Author

aachaemenes commented Sep 27, 2024 via email

@DavidWiseman
Copy link
Collaborator

Thanks for the links. PowerShell commands are not an ideal fit as users would need to enable the Windows feature for the module to be available. The service account would also need access to run these PS commands. I'm unlikely to implement this feature as it's not something I need. As a workaround, you could collect this via PS script, store it in the repository, and create a custom report for it.

Note:
If anyone else is interested in this feature, please comment on this issue. If you are interested in working on it - let me know. Pull requests will be considered.

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