Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

ConfigWizard on SQL AlwaysOn Backends

A support rep recently told me to not run config wizard on our SQL AlwaysOn DB for SolarWinds because we could risk corruption.

Can anyone point me to an article explaining the proper way to update SolarWinds in the future with a AO backend?

I realize AO is not supported, but since this is the suggested method for HA in many threads, I guess everyone is in a pickle using AO.

Thanks

Find more posts tagged with

Accepted answers

mesverrum

That sounds like someone who got burned on a call and is gun shy about a tech they aren't familiar with. I mean to be honest any time you do anything to the DB I guess you could claim that you "risk corruption" but a properly set up SQL AG is not going to be significantly more risky than a regular SQL instance. When in doubt just grab a full backup of the DB before you begin.

There is no general prohibition against using AG's for Orion and I have personally worked in at least 50 environments that have been running it without problems. AG is a supported configuration, it's just that SW support isn't going to help you fix your cluster if it gets messed up. You need to rely on your DBA for that. When the first version of Log Analyzer came out I found it did not properly support AG's and was able to open a ticket and the problem was resolved in the next release, so it's not like the Orion devs act like AG isn't a thing.

All comments

mesverrum

dgsmith80

I wonder if they are referring to stopping/breaking the AAG Cluster prior to running Config Wizard so that it updates the DB on the Primary Node as a single Node, then re-enable AAG to allow replication to do its work? You shouldn't need to do this, but maybe that's what the SE was referring to? Either way, as mesverrum said there are no issues with using AAG's - I've worked with several customers who use it with no problem at all.

hpstech

I have no doubt AO is widely deployed successfully.

This SE was highly technical and great to work with. He gave me numerous off the cuff random tips and tricks in one call.

If there are no considerations for running the CW against the AOL then I’ll take that to the bank.

Thanks guys

hpstech

That is correct, he did mention disabling etc. I should have pointed that out. My post was misleading on that front. I guess I was looking for best practices if they do exist.

Again, this tech was awesome and was going MUCH more in depth in his troubleshooting than any tech I've ever spoken to - its a shame this guy can't answer every call as he knew his stuff at a very high level.