Does Microsoft recommends configuring PWA on a seprate site collection and its Project sites in a different site collection RRS feed

  • Question

  • Hi,

    Does Microsoft recommends having pwa configured on one site collection and its project sites configured on some other site collection.

    For ex pwa is configured at url http://myserver/pwa 

    and project site creation is restricted to url http://myserver/projectsites site collection

    We have a lot of technet article suggesting having PWA site collection in a different database but does microsoft suggests having pwa in a separate database and project sites in some other database.



    Tuesday, April 15, 2014 9:00 AM

All replies

  • Hi Bhawna,

    It depends on the Project Requirements.

    Creating a Project Site on a different site collection helps if you are going to have huge number of Project Sites to be created.

    Here, considering this requirement you can create a site collection on a new content database and get the project sites created on this site collection to help reduce the site of the content database hosting the PWA site collection.

    Cheers! Happy troubleshooting !!! Dinesh S. Rai - MSFT Enterprise Project Management Please click Mark As Answer; if a post solves your problem or Vote As Helpful if a post has been useful to you. This can be beneficial to other community members reading the thread.

    Friday, April 18, 2014 12:57 PM
  • Adding to the above:

    The draw back of using a new site collection is that the navigation bar present beside the site actions wont lead back to the PWA instance.

    Shiva Prasad B C

    Cheers...!!! Happy Troubleshooting...!!!

    Friday, April 18, 2014 8:49 PM
  • Thanks Dinesh and Shiva for your replies.

    We too have created project sites in a separate site collection but this has broken the navigation links in quick launch that needs to point back to pwa site collection like "Schedule" etc.

    Is there some to fix them all up. Because manually fixing all these links is not possible as we have more than 1000 project sites.

    Also, now the users are not getting synced to web admin(pwa synchronized) group.

    Need your help please.



    Saturday, April 19, 2014 4:36 AM
  • That used to be the guidance in 2007, as I recall, when the PWA site wasn't that portable.  In that case, it made it easier to move the sites to a new farm, and attach them to a new PWA site.

    In 2010, PWA backup/restore worked much better, and that guidance fell by the wayside.

    The main reason to put sites in different site collections would be to mitigate database size.  For instance, if one project is expected to have documents exceeding approx. 100GB in size, you may wish to consider putting each project in its own site collection.

    The only issue with splitting them is perhaps some minor navigational elements, and there's a bit of work to deploy the updated Project ribbon on those sites.  There're a couple blogs written for 2010 that describe the effort.

    Andrew Lavinsky [MVP] Blog: Twitter: @alavinsky

    Saturday, April 19, 2014 6:40 PM
  • Thanks Andrew for your reply. 

    Can you please help me understand, that if PWA and project sites are on different site collections then the users does not get sync to Web Administrator(PWA Synchronized) group. 

    Can you please throw some light on the reasons and possible reasons.



    Monday, April 28, 2014 10:55 AM
  • It's probably by design.  The individual sites all get sync'd up fine, and the admin would typically have site collection administrator rights.

    Andrew Lavinsky [MVP] Blog: Twitter: @alavinsky

    Monday, April 28, 2014 1:11 PM