2

So i'm trying to plan out my services in my 2013 build, in this build i will be doing a tier approach, where as before in my old 2010 design, every thing was on one box.

One of the services i'm scratching my head about is the State Services and where to place it.

I plan to have a couple WFE's and a couple App Servers...the app servers would obviously be hosting the services for the farm.

Should i be putting the state service in the default pool on those app servers or should i be putting it in all pools, regardless WFE or APP server...

Improve this question

1 Answer 1

Reset to default
2

Best practice is to put each service in its own service application pool.

For the State Service (see more here http://technet.microsoft.com/en-us/library/ee704548(v=office.14).aspx) I run it on all of the servers in the farm. It is meant to temporarily cache objects for web requests, etc., and is more performant if each server has access to it on itself.

Improve this answer
5
  • So you create a database for each state service you have?...in example...2 WFE and 2 APP servers...4 databases because you are running state on all 4?
    – Jacob A
    Mar 19, 2013 at 17:34
  • No, you only need 1 state service and it runs on all the SP servers.
    – John Chapman
    Mar 20, 2013 at 13:57
  • So if i understand your clarification...you just install it on one server and that takes care of it for the farm, no matter what the scale.
    – Jacob A
    Mar 20, 2013 at 19:18
  • 1
    Correct, a Service Application isn't specific to a server, it's farm wide. Services on Server is where you choose what runs on each server.
    – John Chapman
    Mar 22, 2013 at 1:11
  • Got it...mis understood your initial statement. Appreciate your time.
    – Jacob A
    Mar 22, 2013 at 19:22

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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