Im having one site collection with 5 sub sites utilizing very high space on the content database. Is it possible to move these sites by creating new site collections to different content databases? Will this lead to any design related issues since the master page is same for all the sites?
Add a comment
|
2 Answers
You can do it with using the export and import Sp-web
- Export the subsite using export-spweb
- create a new content Database
- Create a new site collection with blank template
New-SPSite http:///sites/test -OwnerAlias "DOMAIN\JDoe" -ContentDatabase WSS_New_Site - Now import the subsite on that new site collection using Import-Spweb
- Now test.
Keep in mind there are limitation in export/import operation.
Easy method is use the 3rd party tools then move the subsites to new site collections. You can try Sharegate or metalogix etc.(both offer free trial)
answered Jan 3, 2017 at 18:14
-
Thanks for the answer. All sites are Team sites with multiple features enabled: Bulk Workflow, Search, Publishing, CoSign Connector to name a few. Is it feasible to do export and import? Is there any alternate methods apart from third party tools. Jan 5, 2017 at 17:36
-
import& export is the only option but it has limitation regaring workflows etc...– Waqas Sarwar MVP ♦Jan 5, 2017 at 17:45
Your in-box options are using Export-SPWeb and Import-SPWeb. However, those options are not full fidelity and do not support sites with Publishing features enabled.
I would instead look at 3rd party solutions. Or reconsider... how large is the database and what is the concern? Out of disk space on the SQL Server?
-
no, the both commands works well even publishing features are enabled. only thing is it needs a site collection with blank template.– kesavaJan 3, 2017 at 20:38
-
It's absolutely not supported to Export or save a Publishing-enabled site as a template.– user6024Jan 3, 2017 at 20:40
-
i think you didnt get it right! export doesn't give you any template, it generates ".cab" files so those can be imported.– kesavaJan 3, 2017 at 21:00
-
Again, well aware of that and how doing so with a Publishing site is not supported. Working != supported.– user6024Jan 3, 2017 at 21:01
-
1support.microsoft.com/en-us/kb/968483. This explicitly covers what the original poster is attempting to do (take a publishing subsite to a rootweb in a new Site Collection) which also outlines @waqas-sarwar-mvp answer is unsupported. But again, I don't like the
Export-SPWebanswer due to all of the manual fix-ups that would be required. Instead, I'd focus on the database size concern the op has as it is likely a non-issue.– user6024Jan 3, 2017 at 21:12