none
What complications should be considered before creating a new site collection in my SP2013 farm?

    Question

  • Hi,

    I have a SharePoint 2013 Enterprise farm with one site collection. I am receiving storage capacity warnings. Should I keep extending my capacity on the one site collection or start thinking about a strategy to create new site collections? What issues may I hit when creating new sites in new site collections that will have content linking back to sites in other site collections? I currently have Department A, B, C... sites in my site collection, if I decide not to extend my current site collection and create new site collections should I migrate Department A to the new site collection as there won't be capacity to create Department A sub sites in the original site collection? With the migration will I hit issues with Content Query and Content Search web parts?

    Thanks.

    Monday, March 27, 2017 12:58 PM

All replies

  • Hi,

    It seems that you have configured quota template for the site collection. If that is the case, then you can change the quota template with a higher limit for the site collection. After that, you do not need to create new site collection.

    https://technet.microsoft.com/en-us/library/cc263223.aspx?f=255&MSPPError=-2147217396#BKMK_Updatequotatemplateforsite

    Best Regards,

    Victoria

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Tuesday, March 28, 2017 9:43 AM
    Moderator
  • Hi,

    Instead of relying on 1 single site collection, you should create multiple web applications, site collections, managed paths and multiple content databases. use the site quota template to limit the size of the site collection. Regularly delete the old and unneeded data from the site. Use the Quota templates to define how much data can be stored in a site collection and the maximum size of uploaded files. Associate different quota templates with site collections at different service levels.

    you can move different site collection to different databses using below command:-

    Move-SPSite <http://ServerName/Sites/SiteName> -DestinationDatabase <DestinationContentDb>

    Move site collections between databases in SharePoint 2013
    https://technet.microsoft.com/en-us/library/cc825328.aspx?f=255&MSPPError=-2147217396

    Content Query and Content Search web parts will remain intact however please test it in test environment before running it in Production.

    Below is a list of some helpful links :-

    Plan the structure of site collections and sites
    https://support.office.com/en-us/article/Plan-the-structure-of-site-collections-and-sites-a52ec1e9-856f-4bad-81b3-5d16e0777909

    Software boundaries and limits for SharePoint 2013
    https://technet.microsoft.com/en-us/library/cc262787.aspx#SiteCollection

    SharePoint 2013 site collection governance
    https://technet.microsoft.com/en-us/library/cc262900.aspx?f=255&MSPPError=-2147217396

    Fundamental site planning in SharePoint 2013 (How will the site or solution be structured and divided into a set of site collections and sites?)
    https://technet.microsoft.com/en-us/library/ee476994.aspx

    Application management and governance in SharePoint 2013
    https://technet.microsoft.com/en-us/library/dn531035.aspx

    Let me know if this helps. Feel free to get in touch in case you need further help.

    Thanks, Vandana Rathore (MCSE, MCTS, PRINCE2®) |(Please remember to click on “Mark as Answer” if this post helps you)


    Tuesday, March 28, 2017 12:13 PM
  • HI,

    Were you able to create SharePoint site collection using the best practices? Let us know if any of the above suggested links helped you.

    Please remember to mark the replies as answers if they help.

    Thanks, Vandana Rathore (MCSE, MCTS, PRINCE2®) |(Please remember to click on “Mark as Answer” if this post helps you)

    Monday, April 24, 2017 4:07 AM