none
Differences Between Multi Tenancy and Creating Multiple PWA Instances on 2013

    Question

  • Hello;

    I've read about multi tenancy support. Actually I cannot find any documentation for Project Server 2013 multi Tenancy. I want to learn that. What is the differences between Multi Tenancy support with sharepoint and Multiple PWA instances?

    Also, I wonder that which one is more suitable for a compant that want to seperate their Project Servers from each other?

    Thanks for the answer

    Thursday, November 21, 2013 12:04 PM

Answers

  • Hi Burak --

    When you provision a new PWA instance in 2013, you must specify a SharePoint Web Application under which to provision the new PWA instance. When you create the new web application, you can assign it a separate SharePoint content database; therefore the data stored in the Project Sites, such as Risks, Issues, Documents, etc. will be in that separate content database.

    Good luck!

    -- tz


    Tony Zink | Vice President, EPMA | http://www.epmainc.com | Blog: http://www.epmablog.com | Training: http://www.epmainstitute.com

    Thursday, November 21, 2013 7:29 PM

All replies

  • Hi Burak --

    Multi-tenancy is more relevant to SharePoint 2013 than Project Server 2013, but since Project Server runs inside of SharePoint, Microsoft mentions it in their marketing materials.

    Multi-tenancy in SharePoint 2013 provides more separation of data and services between tenants / groups, and I see it typically being used in scenarios where multiple companies are sharing the same SharePoint farm through a SharePoint hosting company (or Microsoft SharePoint Online). Those companies obviously want their "stuff" to be completely separated from other companies who are sharing the same infrastructure, so Microsoft provides more of that separation in SharePoint 2013 than they did in SharePoint 2010. There is also a tenant administration layer that is added below the Central Administration layer where each tenant has a certain level of control over how services are configured within their silo.

    If you are deploying SharePoint 2013 within a single company, however, you probably do not need to complicate your implementation by enabling multi-tenancy... unless it is a huge company with several large divisions who want more separation between them. Provisioning multiple PWA instances -- assuming that the groups want complete separation of their data, resource pools, etc. -- will probably meet your needs.

    Here is some good information about SharePoint 2013 multi-tenancy:

    http://www.harbar.net/articles/sp2013mt.aspx

    http://www.dummies.com/how-to/content/sharepoint-online-farm-multitenancy.html

    Contact me directly if you would like more help.

    Good luck!

    -- tz


    Tony Zink | Vice President, EPMA | http://www.epmainc.com | Blog: http://www.epmablog.com | Training: http://www.epmainstitute.com

    Thursday, November 21, 2013 5:50 PM
  • Hello Tony;

    Really thanks for tour answer. You said "complete seperation". I wonder that if I use multiple Project Server Instances instead of multi tenancy, how can we use seperate PWA Content databases for each instance? Forexample, if I use different site collections for each pwa instance, is that cause a performance issue or something?

    Thursday, November 21, 2013 6:49 PM
  • Hi Burak --

    When you provision a new PWA instance in 2013, you must specify a SharePoint Web Application under which to provision the new PWA instance. When you create the new web application, you can assign it a separate SharePoint content database; therefore the data stored in the Project Sites, such as Risks, Issues, Documents, etc. will be in that separate content database.

    Good luck!

    -- tz


    Tony Zink | Vice President, EPMA | http://www.epmainc.com | Blog: http://www.epmablog.com | Training: http://www.epmainstitute.com

    Thursday, November 21, 2013 7:29 PM