SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

My current farm(meduim) have all Service Applications in separate app pools and accounts. But we are planning to split and configure all service application under a single application pool.

Please tell me the impact of this change.

share|improve this question

Consolidating your service applications pool into a single one will impact your farm, no doubt about it, but both in positive and negative ways.

Let's start with the bad ones...

  • You will not have process isolation.
  • For instance the SSO service should have it's own process for security reasons
  • If one service app dies/crashes, all of your service apps will
  • You don't have a granular way to set permissions on the different service apps
  • You will need to revisit your SLA's

And now the good ones..

  • You will consume less memory with fewer application pools, thus impacting performance
  • It is far easier to manage

So a single one might not be ideal, except in development environments, but keep it as few as possible to live up to SLA's and security levels.

There are probably tons of more of both pros and cons (if you got a few add them as comments and I'll update this answer - all for the sake of the community :-)

share|improve this answer
OK Thanks for your input – Mohan Periyasamy Aug 15 '11 at 10:21

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.