Co-habitating SQL instances
I'm doing resource planning for our 6.1 deployment. Instead of setting up a separate HA dbase, I'm wondering if it is practical to host the Archer DBase instance on our departmental SQL server, where it would co-habitat with numerous other DBs. It would certainly make my life easier...
Anyone else running their production environment this way? Assuming physical resources are not over subscribed, are there any gothas I should be aware of? The sizing guide says the DB should be on a separate server (which can be interpreted a couple of ways), would this setup be supported?
- Community Thread
- Forum Thread
- instance database
- RSA Archer
- RSA Archer Suite
- Tips and Tricks
Yes, the setup you describe is supported, it's just not recommended. Archer is a very SQL intensive application, so we recommend isolating it on a box where it's the only thing consuming resources.
That said, provided you have an adequately sized SQL box, and it's configured according to the Archer guides for recovery type, degrees of parallelism, and so on, you can certainly run it in a co-located environment.