none
Draw backs of more than one Project Server Instance RRS feed

  • Question

  • What are the draw backs of creation of more than one project server instance in the organization ?

    Is it better to create one project server for all big organization or more than one ?

    Thursday, June 21, 2012 2:02 PM

All replies

  • Mostly admin and maintenance costs/issues. 
     
    First rule of thumb is to combine them if they use shared resources.  If
    not, then it's a question of whether or not their security and configuration
    requirements are close enough to coexist - and if they're willing to grant
    security to shared administrators.
     
    That being said, it's pretty typical to see a large organization have multiple
    instances: IT, Ops, etc.
     
     

    Andrew Lavinsky [MVP] Blog: http://azlav.umtblog.com Twitter: @alavinsky
    Thursday, June 21, 2012 3:07 PM
    Moderator
  • Hi John,

    This is a very wide topic to discuss; it all depends on business requirement, hardware availability, geographical location of the user etc.

    http://technet.microsoft.com/en-us/library/hh297440

    Christophe’s article may help you on this topic

    http://blogs.msdn.com/b/chrisfie/archive/2010/07/02/project-server-2010-and-sharepoint-2010-one-farm-or-multiple.aspx


    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < | LinkedIn

    Thursday, June 21, 2012 3:07 PM
    Moderator
  • Hi John,

    Geographical locations really drive separation of PWA instances quite a bit due to communications latency. SharePoint requires a latency of 120ms or less and communications with Asia Pacific regions for Project Professional can be especially problematic in this regard. I see a lot of NoAM, EMEA, APac type PWA divisions to keep local.

    Otherwise, Andrew is correct with maintenance cost and security for other driving factors.

    Our typical installation has a Test/Staging instance, a Production instance and a Training instance of PWA. Multiply that times the number of PWAs and you start to see the maintenance issue. Tools like the Playbook tool help but you still have to have rigorous change management in place to keep things in sync.

    You might want to review the Department feature, as it was designed to reduce the need to have separate PWA instances. It allows each business unit to have it's own set of custom fields, Enterprise Project Types and OLAP databases within a single PWA instance.

    Performance is another concern. There's another thread in the forum of a user having an issue loading 8000 projects in a Project Center view. One big instance could lead to situations like this.

    Treb Gatte

    Thursday, June 21, 2012 4:50 PM
    Moderator
  • Have just installed PS2010 in a global env, with locations in APAC, US and Europe, with servers in Europe.  We had WAN issues, which highlighted issues in the customer's infrastructure (global catalogues not located in each region, lots of domains etc, and some pretty poor WAN links in APAC).  All issues have been identified and are in resolution, so it is possible.  A single soln was a must for this CU, as they perform global projects.  Also, setting expectations really helped by helping PMs and TMs understand where the data was held, and what the Q's etc are doing.

    Ben Howard [MVP] blog | web

    Thursday, June 21, 2012 7:32 PM
    Moderator