There is one thing that I didn't see mentioned anywhere in the forums or on the SolarWinds website that I wanted to let everyone know about.
If you decide to install the SQL database on a different server than the Orion NPM install or if you decide to split the SQL database off of your existing Orion NPM install make sure that you keep this in mind:
1. You can reboot the Orion server with out all of your alerts being triggered once it comes back up.
2. If you need to reboot the SQL server, Make sure that you disable all alerts first, reboot the SQL server, then wait for an additional 3 to 5 min before enabling the alerts again or all of the alerts that you have setup will be triggered. (i found this out the hard way and had 300+ email alerts and resets sent out to upper management, Distributed Systems, and a few dozen other departments).
3. You will need a way to stop the Orion services before maintenance schedules and turn them back on after. I have created 2 bat files that will do this and set them up in Scheduled tasks on the server. So far, no more alerts and resets being sent out for reboots.
4. if you choose to use a bat file to stop and start the services, make sure that you change the service startup to manual. Otherwise, if patches are applied during maintenance. and forces the server to reboot, the services will start before you want them to, and if a second server reboot happens the alerts will get sent out.
The .bat files are not difficult to create, but if anyone wants, I can post them here and on the Content Exchange.
