Multiple MOPS 07 Instance - Technical Citations

A

Andrew Lavinsky

Just questioning some assumptions, and wanted to throw this question out to
the newsgroup. I've always practiced a policy of not deploying multiple MOPS
instances in a PROD environment due generally to the complications that such
a deployment brings.

Now my client is asking me if there's any specific Microsoft guidance
regarding why it's generally bad to deploy multiple instances in a PROD box
(assuming that they're deployed in their own content dbs, web apps, etc.).
All I could dig up was some guidance on internal hosting on Technet.

So I guess my question is.....what is the "official guidance" (if such
exists) on whether or not it makes sense to deploy multiple instances on a
single 3-tier server farm. And if I can't identify the "official guidance,"
what's the general consensus of the folks on this group?
 
B

Ben Howard [MVP]

Hi Andrew

I can't recall any official guidelines per se, but there is a suggested
limit on the number of SSPs per web farm (4?), which is going to limit the #
of content DBs if you want these separated for each instance.

It all comes down to per, as you'll be well aware. I've one CU with two
prodn instances on a 2-tier app, with two lightly used test instances). The
only perf mods I changed where to turn off scheduled cube building for the
test instances, and lowered the timesheet thread settings. It all works
nicely, but then they do reboot the box every week, which might say something
in itself!
 
G

Gary Chefetz

Andrew:

I've never seen anything but encouragement for this arrangement, not
cautions against it. I think that multiple instances work fine in production
particularly if they all serve the same audience such as Production,
Training and Sandbox. Multi-tenancy situations deserve other considerations.
 
Top