Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

We are looking at the possibility of migrating 2TB+ worth of data from our network driving into SharePoint for a department site. For this question I'm assuming all data is valid and has the ability to be assigned to a custom content type and be given basic metadata.

If we did this, we would need to split the data between multiple site collections / content databases but ideally the user experience would be fairly seamless. Key functionality: - Users will be collaborating on about 5% of the content at any one time but we don’t currently have a way of determining what would be considered collaborative content and what would be classified as a record. Technically we do but I don’t believe the business is willing to do that on a document by document basis.

  • Users can browse to their content
  • Users can search for their content
  • As more content is added we will need to add additional content databases. Existing content may need to be moved to those content databases but the experience should stay constant. I.e., I’m trying to avoid the scenario of documents used to be in SiteA/DocLib1 but now you have to go to SiteB/DocLib1.

Question

What concepts / whitepapers should be researched in order to evaluate this?

share|improve this question
    
What version of SP and SQL server are you running, that might be beneficial. –  PirateEric Apr 2 '13 at 18:19
    
SharePoint 2010 and SQL Server 2008 R2 –  RWL01 Apr 2 '13 at 21:54
add comment

1 Answer 1

up vote 1 down vote accepted

For such a large database, you should create site collection with separate content db. You can't do this through UI, so you have to create the structure programmatically.

You can refer following whitepaper: Managing Multi-Terabyte Content Databases with SharePoint 2010 (white paper)

Hope it helps!!

share|improve this answer
    
Thanks for the information, it told me what I need to know which is unfortunately managing multi TBs is not really what SP does best. We've decided to push these requests into our Documentum system and referece that data through custom webparts in SP. –  RWL01 May 3 '13 at 13:49
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.