Creation of dynamic site collection and sub-sites

We are having an enterprise system where organization wide operations are maintained. Recently we decided to provide collaboration features for each operation maintained in the system using SharePoint 2013, since that enterprise system did not provide
any social/collaboration features.
Assumptions/constraints -
1. Every year 2500 operations are created
2. Each operation can have documents and other content scaling upto 5 GB.
3. Only SharePoint provider hosted apps are allowed to build the solution
For seamless integration, we are creating an automation component which will a SharePoint provision site automatically when an Operation is created in the enterprise system (we will get the trigger through web services)
Proposed solution - 
After going through
Software boundaries and limits for SharePoint 2013, I'm thinking of proposing this architecture -
 1. A windows service will be created which will accept the trigger to create a site and take care of provisioning the entire site 
 2. A maximum of 700 sites will be created per site collection (based on the size calculations and keeping some buffer)
 3. Once a site collection hits 700 sub-sites, a new site collection is automatically created for provisioning the new sites
 4. Provision the apps and add them to site pages using powershell/CSOM
Kindly let me know if this approach is effective or any major road-blocks we need to take care of in this.
NLV - MCTS - Blog -
Twitter - In

Hi Margriet,
We are looking at the SharePoint 2013 limitations and trying to devise the best possible solution. We are open to create multiple content databases for multiple site collections or with single contentdatabase having multiple site collections (which doesn't
look like feasible). So it is a matter of deciding which will best suit this scenario.
NLV - MCTS - Blog -
Twitter - In

Similar Messages

  • Site collections, or sub-sites, in SharePoint Online?

    We have an established SharePoint 2010 intranet portal, which has many and various team sub-sites.  These sub-sites are created on request - sometimes it's because one of our locations wants their own little area to share documents, or it might be for
    a company-wide project or initiative.
    We are now slowly moving over to SharePoint Online.  Mainly, it's to replace Box and Dropbox (which some teams use), and allow our staff to share files externally if needed.  Nothing special, just a document library.  More often than not,
    each site will have its own unique permissions.
    Now, our SharePoint 2010 site is one large site collection (wasn't my idea).  As an administrator, that makes my life quite easy as it's one content database, one set of content types, etc.  But, with SharePoint Online, I don't need to think about
    content databases, and won't be using custom content types with these sites.
    So, I'm a bit stuck.  My options, as I see it, are:
    One large site collection (pretty much a no-go as these shared files might get quite large)
    One site collection for each request, no questions asked (which might lead to hundreds of site collections)
    Create a site collection for each office location, and then a sub-site for each team in that location (as requested) - and also create a site collection for each company-wide function, and create a sub-site for each project within that function
    Can anyone give any pointers towards the "best" option to use here?

    it always depends on different things. 
    One of the key elements I always use to decide site vs site collection is security boundary.
    If the target site has a high level of confidentional information, I prefer a dedicated Site collection.
    If it is just a smaller team (or broader team) to share info with you can easy use sub sites.
    Looking at the boundary & limits is also wise to do. (like the 5000 item treshold in a view on a document library)
    A document library should in practice not really be used for multiple teams, however it is possible. A lot of dl's within a site is also not that intuitive for a lot of end-users.
    A office location can be use, however, a lot of work is done across office locations. (now or in the future)
    One site collection per each request is not by definition a bad thiing... however please be in control (governance) of the owners. For example let a site collection owner every x months acknowledge that he/she still needs that site collection or that it
    can be removed.
    One Large site collection is asking for trouble in the end. however for a publishing intranet only it can be good.
    Good luck with your choice for your environment!
    You can also contact me if you want to discuss more on this topic.
    Michiel Hamers www.SharePointman.nl Don't hesitate to contact me for a SharePoint/O365 question.

  • How to deploy site collection has sub sites to other environments

    Hello everybody,
    I have a site collection SharePoint online.
    In the site, haven 3 sub sites.
    Now, i want to deploy this site to other environment,
    How can i do that?
    I am trying save site as template but that is not support sub site.
    Thanks and best Regards,
    QuyenPV

    Hi,
    According to your post, my understanding is that you want to backup SharePoint online site to another environment.
    For SharePoint server, we can use the PowerShell to backup the site collection with all the subsites.
    However, per the technet article below, there is no backup and restore cmdlets for SharePoint online to backup and restore.
    http://technet.microsoft.com/en-us/library/fp161374.aspx
    You can use the third-party tool to achieve this scenario.
    http://blogs.technet.com/b/akieft/archive/2012/01/09/restore-options-in-sharepoint-online.aspx
    As this is the forum for SharePoint server on-premise, I’m not familiar with the SharePoint online, for this issue, I recommend you can post a new question in the forum for Office 365/SharePoint online.
    http://community.office365.com/en-us/forums/154.aspx
    More experts will assist you, then you will get more information relation to SharePoint Online.
    Thank you for your understanding and support.
    Thanks & Regards,
    Jason
    Jason Guo
    TechNet Community Support

  • Get Sitecollection and Sub Sites Data Base Size Using PowerShell

    Hi All,
    Currently i am getting the Site collection database size using this powershell
    $SiteCollurl = @{Expression={$_.url};Label="Site Collection URL"}
    $size = @{Expression={[math]::round($_.diskused/1MB, 2)};label="DB Size in MB"}
    $HTML = Get-SPSiteAdministration -Limit All | select $SiteCollurl, $size
    So in this $HTML i am getting all the Site Collection Url's and DB size for each site collection.
    Now i want to get the Sub Sites url and Sub Sites Database size also.
    I tried like this  "$HTML = Get-SPSiteAdministration -Limit All | | Get-SPSite -Limit All | Get-SPWeb -Limit All  | select $SiteCollurl, $size"
    I am getting all the sub site url's but Database size i am getting 0 for all sites and sub sites.
    Can any one help on this.how to get the database size for all site collection's and sub sites.
    Regards,
    Phani.
    Rhys W Edwards Where are you :)

    Hi
    Please try the script below:
    Get-SPSite -Limit ALL | ForEach {
    $_ | Get-SPSiteAdministration | Select $SiteCollurl, $size}
    I hope this helps.

  • Best Practice for Host Named Site Collections and Web Apps

    Looking for advice on setting up the host named site collections.  If I am reading many of the technet articles and blogs correctly I should 1) have only 1 top level web app for host named site collections and 2) not have a host header for that web
    app.  If that's correct I am looking for advice.  We have 7 separate domains that we support in our farm.  Currently each of those domains is divided into web applications based on the domain,  *.contoso, *.trains.com, *.bakers.com, etc.
      Is the concept now that all of the host named site collections fall under that one web app?  How do we deal with the SSL for each of those separate domains which all have their own certificates? 
    Thanks in advance for your comments. 
    NLewis

    Yes, for creating host named site collections, first you create a host header less web app and then create host named site collections under that web app. However this is only for the cases where all the host named site collections ends in one domain. So
    you can create host named site collections as intranet.contoso.com, my.contoso.com, portal.contoso.com etc as they are all ending in *.contoso.com.
    As per your environment, if you have web apps which caters to different domains like *.contoso.com, *.trains.com, *.bakers.com, you need to create separate web apps as they are all ending in different domains. Then you can have a separate wildcard SSL certificate
    for each of those web apps.
    Hope this helps.
    Thanks
    Mohit

  • Search does not crawl new site collection and documents

    We have the following situation. We have two locations with different farms sharing the same databases (using AlwaysOn for the content databases). Everything works fine, the second site is also read-only while having the primary farm online. For existing
    databases the search crawler on the second site is able to crawl existing site collections.
    For new site collections created on the first farm the crawler on the first farm indexes the content proberly. The second farm though is not knowledgable of the content unless you force him to reiterate the content database. After this procedure the sites
    are available on the second site as well (showing them in the web browser), but the search farm still is not able to see the new site collection and data created within.
    Is there any additional iteration we have to go through making the crawler aware of the new structure / content ?
    Thanks in advance, Jens

    Nope.
    Change log wipes are real, that's how incremental crawls work in SharePoint.
    Site A is created and modified. Changes are mirrored to the second AG, content is added, logged in the changes log and then removed as the crawler on the primary farm indexes it.
    This continues until you make farm 2 aware of the changes. At that point farm 2 will look for any changes to the content in the change logs on the newly added sites. Which will be empty, or at least not contain any changes since the primary farm's last crawl.
    That explains why you don't get sites indexed properly when they are added but would explain why some content is indexed afterwards which i believe is the case?
    The second issue you'll find is that the crawls won't synchronise. Assuming continuous crawls kicking off at the same time you'll end up in a race between the two. If the primary farm is quicker then the second farm will continuously fall behind then catch
    up and go ahead of the primary indexing process, but if the secondary farm is faster then it'll race off into the distance and then any changes that occur between the secondary farm indexing a site and the primary indexing the site will be lost on the secondary
    farm.
    You'll have to run full crawls. Unless MS have done a lot of work on the supporting infrastructure incremental or continuous crawls of AOAGs won't work well.

  • MySite as a Publishing Site Collection (for Cross Site Publishing)

    Hello,
    is it possible to connect the MySite in SharePoint with an Product Catalog? I have an Authoring Site Collection and a MySite Collection. In the MySite i have allready activated the Publishing Feature and then connected my Catalog from the Authoring Site.
    After that i've made a Navigation from the Term Store Management Tool.
    The Problem is, that i cant see any changes an no Navigation at the MySite.
    Is it somehow possible to get it working?
    Thanks

    Hi Arnold,
    As MySite use My Site Host site template in SharePoint, so the master page is different and MySite use custom master page for rendering the navigation.
    If you want to use Managed Navigation for MySite, then you need to create a custom master page for rendering the terms in navigation.
    Here is a similar thread for you to take a look:
    https://social.technet.microsoft.com/forums/sharepoint/en-US/5c48c32f-f102-4935-83d3-1ba06be072ec/using-managed-navigation-for-my-sites
    Here is a link for creating a custom master page for rendering the managed navigation:
    http://blogs.c5insight.com/Home/tabid/40/entryid/378/SharePoint-2013-Managed-Navigation-Lessons-Learned.aspx
    Best regards.
    Thanks
    Victoria Xia
    TechNet Community Support

  • How can I publish the alterations I have made to my iWeb pages when the ' Publish Site' button and 'Publish Site Changes' on the file dropdown are grey?

    How can I publish the alterations I have made to my iWeb pages when the ' Publish Site' button and 'Publish Site Changes' on the file dropdown are grey?

    this is a perfect question for the users in the iWeb forum.  https://discussions.apple.com/community/ilife/iweb.  Good luck.

  • Cust site ID and Cust Site Dyn

    Hi,
    Can some one please help me to understand the difference between Cust Site ID and Cust Site Dyn? where it is maintained and Can a sales order have both these? Tcode/ Tables?
    Please explain at a begginer level, as I am not a SD consultant.
    Regards

    Jith,
    you probably need to give more information on which context you came across these 2 fields. Do you have field names? Which system?
    This will help you to get a better feedback.

  • MySite Host Site Collection "Site Settings" Menu and sub-site creation

    Seemingly by design, users are able to create sub-sites on the MySite Host site collection when the configuration instructions here are followed: Configure My Sites in
    SharePoint Server 2013
    To be a little clearer, as instructed, I've created and applied a subsite-creation user policy to the web application hosting the MySite host. Presumably, this enables sub-site creation in personal MySite site collections. Perfect.
    Except... this also enables creation of subsites on the MySite host itself.
    If a (non-administrative) user clicks the cog from the Newsfeed page, the scope is the MySite host.
    The "site settings" link leads to the site settings of the MySite host.
    There, in the  "Sites Administration" section is "Sites and Workspaces".
    ...and there, is the option to create a new sub-site at https://my.contoso.net/. -_-
    How might I avoid this undesirable state of affairs? I would like to give users the ability to create sub-sites in their own MySites, but not on the MySite host via the Newsfeed page. Is this possible?
    I think I can. I think I can.

    This is definitely possible - So you enabled self-service site creation in Central Admin per the configuration instructions. Did you also create a user policy on the web application?
    In my tenant non-admins do not have access to click site settings on the mysite host (They can click site contents, which redirects to the personal site collection). Also, they do have access to click site settings on the personal mysite site collection
    though.
    Regards,
    Andrew J Billings
    Portal Systems Engineer//MCSA,MCSE
    Blog:
    http://www.andrewjbillings.com 
    Twitter:
      LinkedIn:
    I did some testing and figured it out, I think. Mind you everything worked properly, users just had access I didn't want them to.
    I did enable self-service site creation, and I created the user policy on the web application as per the instructions. I then discovered users had access to site settings on the Newsfeed page: https://my.contoso.com/default.aspx
    The only site setting they had access to was subsite creation: https://my.contoso.com/_layouts/15/newsbweb.aspx , but I didn't want them to be able to create subsites on the host, just in their personal collections.
    Deleting that user policy removed their access to subsite creation on the host, and still allowed self-service site creation, and the creation of subsites in personal collections, so the question now is:
    Why are we being directed to create that user policy in the first place, when it doesn't appear to affect personal sites at all?
    I think I can. I think I can.

  • Unable to configure site mailbox at the sub site level and new site collections created

    hi all,
    i am trying to get the site mailbox up in my  SP 2013 env's sub sites and site collections.
    i am able to get the site mailbox created on root site collection level ONLY.
    but i am getting the error  code 8 when i try to add the site mail box at the sub site level and the newly created site collections on the same web appln.
    error code 8:
    An error occurred during the OAuth handshake between SharePoint and Exchange. This is typically caused by server to server configuration issues, such as a realm value mismatch on either side, certificate issues for Exchange or SharePoint, etc. Review certificates
    and attempt to establish or reestablish trust.
    so is it possible to create site mailbox at the sub site level [ team site] ?
    and  what are the  steps i needed to perform on exchange server level.

    hi all,
    i am trying to get the site mailbox up in my  SP 2013 env's sub sites and site collections.
    i am able to get the site mailbox created on root site collection level ONLY.
    but i am getting the error  code 8 when i try to add the site mail box at the sub site level and the newly created site collections on the same web appln.
    error code 8:
    An error occurred during the OAuth handshake between SharePoint and Exchange. This is typically caused by server to server configuration issues, such as a realm value mismatch on either side, certificate issues for Exchange or SharePoint, etc. Review certificates
    and attempt to establish or reestablish trust.
    so is it possible to create site mailbox at the sub site level [ team site] ?
    and  what are the  steps i needed to perform on exchange server level.

  • Granting users Site admin to All site collections and/or Adding an o365 group by email to site admin group on all Site collections

    We will have 1000s of site collections.
    Why doesn't SharePoint Online 2013 offer a way to grant a user or a group Site admin rights to all site collections?
    And.. if we must add the user to every single site, can this be done by an o365 or ADFS group using it's email?
    We'd like to run this script to add a group to site collection admin on all sites, but Groups can't be referenced by an email?
    Get-SPOSite|foreach{Set-SPOUser -Site $_.Url -LoginName [email protected] -IsSiteCollectionAdmin $True}
    produces an error.  And if we try to add the group by email manually through the UI it can't find it either.   We've tried this with o365 groups and  ADFS groups.
    Any way to reference these groups from PowerShell?
    Is this limitation there for a reason? 

    bump.. anybody?

  • Granting permissions to manage my sites site collections and user profiles

    We currently have no governance in place to deal with user profiles and my site site collections.
    So the farm has quite a large number of both profiles and site collections which are orphaned. We do not currently run the timer job that deletes my site site
    I have a few questions about handling this kind of thing.
    1. We have administrative staff who handle the "off boarding" process. They send out mail to people asking whether project folders continue to be needed, etc. and give project members a month to make copies of the important info. Right now, there
    are a few of these staff which have site collection admin rights on normal projects.
    Is there a way that a powershell script could be constructed to give them the ability to delete obsolete user profiles and site collections without giving them full farm admin rights?
    2. Is there a way to set up an AD or SharePoint group and then use that group as a secondary site collection admin on the my site site collections?
    3. With appropriate permissions, would they be able to grant someone else permission to look at data in the my site collection to determine whether any of it needed to be kept?
    I have been requested as a sharepoint admin to work with the offboarding process staff so that they include the sharepoint my site data in the data that they recommend people check before deleting the data.
    I would like to automate as much of the dealings they have to have with the system as possible, just to reduce unrelated accidental actions.

    1. We have administrative staff who handle the "off boarding" process. They send out mail to people asking whether project folders continue to be needed, etc. and give project members a month to make copies of the important info. Right now, there
    are a few of these staff which have site collection admin rights on normal projects.
    Is there a way that a powershell script could be constructed to give them the ability to delete obsolete user profiles and site collections without giving them full farm admin rights?
    Inder : 
    http://blogs.msdn.com/b/kaevans/archive/2012/06/25/top-recommendations-for-managing-the-my-site-cleanup-timer-job.aspx
    http://www.harbar.net/archive/2011/02/10/account-deletion-and-sharepoint-2010-user-profile-synchronization.aspx
    http://blogs.technet.com/b/seanearp/archive/2009/03/04/sharepoint-profile-cleanup.aspx
    2. Is there a way to set up an AD or SharePoint group and then use that group as a secondary site collection admin on the my site site collections?
    Inder: NO, it has to be a user. But you can go to site action > site settings > site collection administrator > Add that group here.
    3. With appropriate permissions, would they be able to grant someone else permission to look at data in the my site collection to determine whether any of it needed to be kept?
    Inder:  Yes
    If this helped you resolve your issue, please mark it Answered

  • How to publish an Admin-Approved InfoPath template to 2 different site collections, and retain same internal column names

    Hi,
    I am wondering how best to publish an InfoPath form as an Admin-Approved template, to both Site Collection 1 (SC1) and Site Collection 2 (SC2). Some fields are promoted to SharePoint columns.
    I have already published my form to SC1, by choosing Publish to SharePoint Server > chose SC1 > Admin-approved > chose to publish to columns I had created manually on SC1 (these columns had relatively user-friendly internal names such
    as 'Form_x0020_Status' etc, which I reference in xsl + code). I then uploaded the template in Central Admin as Admin-Approved, and activated the feature on SC1. This all worked fine.
    However, if I then go to activate the feature on SC2, it creates columns with different internal names (GUIDs), which means my xsl + code won't work. If I try creating columns manually on SC2 before publishing, it still creates new GUID columns.
    This of course must be because on feature activation on SC2, it cannot find the exact columns specified in the template (which was published to SC1), so it creates new ones.
    In that case, what is the best way to publish an Admin-Approved template to 2 different site collections? One option is to create the columns using code, and deploy them to both sites as a feature, ensuring all IDs are the same. But should this be necessary, is
    there any option available using only InfoPath and SharePoint?
    Thanks for reading.

    Check these similar threads
    Republish
    existing InfoPath Form to a different SharePoint Site
    How
    to Programmatically Publish an InfoPath 2010 Template (.xsn) to Multiple SharePoint Sites
    Hope it will help
    Please 'propose as answer' if it helped you, also 'vote helpful' if you like this reply.

  • Host Header Site Collection and Web App Setup - Thoughts

    I am trying to understand relation between AAM and web app extension .Please share your expert opinion. I have not seen any TechNet article talking about it clearly.
    Here it goes: in 2010 it was recommended Not to use AAM with IIS bindings without extending the web application. This was mentioned in several TechNet articles also its  a known “Mistake #4” on TechNet articles.
    So question is, is that still the same case in 2013?
    Most of the times it is recommended to remove web app host header from IIS if you are using this web app for HHSC, otherwise sites will not be accessible. I have find no issues by leaving web app host header and adding more bindings for host header site
    collections any thoughts on this ?
    Thanks. 

    Hi,
    I found some articles for helping understand Extend web application and
    Alternate access mappings.
    “If you want to expose the same content in a Web application to different types of users by using additional URLs or authentication methods, you can extend an existing Web application into a new zone. When you extend the Web application into a new zone,
    you create a separate Internet Information Services (IIS) Web site to serve the same content, but with a unique URL and authentication type. An extended Web application can use up to five network zones (Default, Intranet, Internet, Custom, and Extranet). For
    example, if you want to extend a Web application so that customers can access content from the Internet, you select the Internet zone and choose to allow anonymous access and grant anonymous users read-only permissions. Customers can then access the same Web
    application as internal users, but through different URLs and authentication settings..”
    After you extend web application, there is a new site created in IIS but the content are the same. We extend it to a new zone for different authentication methods, so that we could support different security between Internet site, Intranet site and Extranet
    site.
    “Alternate access mappings direct users to the correct URLs during their interaction with SharePoint 2013. Alternate access mappings enable SharePoint 2013 to map web requests to the correct web applications and sites, and they enable SharePoint 2013 to
    serve the correct content back to the user.”
    AAM is to offer different urls to users to access one site. Sometimes the url of a site is not easy to remember , we could use AAM to create simple url.
    Regards,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected] .
    Rebecca Tu
    TechNet Community Support

Maybe you are looking for