Service Manager - SQL Server High Availability query
Sean_Terry
Customer Advanced IT Monkey ✭✭✭
We are looking at SCSM, Orchestrator 2019 and we have been investigating if SQL Server High Availability would help us. We have a chunky SCSM environment with the warehouse being used for reporting. Would be interested to hear experiences of switching to this, especially with larger deployments. I wondered how any improvements stacked up against any additional costs.
Fairly new to the whole SQL Server High Availability concept so any use cases would be helpful and how you may have gone about providing evidence to support a case for moving to this.
0
Answers
We went HA with both Orchestrator and Service Manager with the Quorum in AWS. Didn't work well for us. The Orchestrator database in encrypted. The first issue is when you synchronize the databases you have to backup and restore the key. Not a big deal but a pain for DR. Never for the value add from Orchestrator HA and are using SRM. As far as Service Manager when we upgrade we are pulling the backend out of HA. TO many issues with keeping our huge databases in synch even across a pretty fat WAN pipe.
We used the standard keep these mission critical apps HA. Just never saw the ROI for the additional overhead.
It really depends on your business needs.
We have running a two node always on SQL cluster supporting SM, SCORCH. DW database. Our SQL made use to use the same keys for SCORCH so fail-over and DR is not an issue. For our community size and needs we went with a design of the high performance DBs to run on local SSD's. The DW runs on a external network storage. Then for TempDB we placed basically direct storage memory. With the two node cluster we can fail over at any time for max uptime.
But basically the key to any design is your IO on the disk to support the users, and the required uptime.
HTH
Agree with all of the above.