SharePoint Products TechCenter >
SharePoint Products and Technologies Forums
>
SharePoint - Setup, Upgrade, Administration and Operation
>
Large document library
Large document library
- Hello,
I have following problem:
I have a document library with 50000 documents, that is occuping (so far) 30GB of storage, the number of docs is increasing very quickly, and within one or two years can go above 100GB, i think this is more than the recomended size for a content database.
Will it be a good solution to split the documents into several Site Collections (one doc library on each) and put each SC in a separate content database?
THanks in advance,
jv
João Vilela- Moved byMike Walsh MVPMVP, ModeratorMonday, November 09, 2009 11:51 AMadmin q (From:SharePoint - Enterprise Content Management)
Answers
- Exceeding 100GB isn't necessarily going to break anything as you are aware. I know of installations that have content DBs twice that size and things seem to work ok. Is it recommended, probably not, but they get by. On the other hand, I know other admins that swear by never letting the db exceed 50 GB as well. I would probably do my best to try and stick to the published recommendations.
Corey Roth blog: www.dotnetmafia.com twitter: twitter.com/coreyroth- Marked As Answer byGuYumingMSFT, ModeratorTuesday, November 10, 2009 1:18 AM
- Unfortunately, there is no single recommendation Microsoft can make that caters to all possible scenarios working acceptably and performantly. However, the published document(s) which lend to the 100GB recommended size are what we feel to be acceptable for a wide range of scenarios.
For what it's worth, scaling across content databases is the best you will get when it comes to performance -- but as you can also appreciate it comes with added administration overhead; in this case splitting up your document library.
List size is more related to (doesn't mean it's not related, but less so) rows in your content database, rather than the size of the data itself, in fact this becomes even more apparent in SharePoint 2010. So I'm comfortable saying yes you can have 100GB in one content database -- at the same time, also look at this from the perspective of other admin tasks like Backup/Restore. Particularly if you're reaching 5TB of data storage in a content database, I have to say Backup-Resotre will be quite a task.
I wouldn't go the SC route really, the max recommended number there is largely relevant for the Profile and MySites feature -- plus if it doesn't make logical or semantic sense for your data to be organized that way, don't do it!- Marked As Answer byGuYumingMSFT, ModeratorTuesday, November 10, 2009 1:14 AM
All Replies
- If your growth rate is pretty high then yes, I would probably recommend being proactive and start looking at how you can split things into different content databases. It would be better to have a plan for it now than later once the database gets quite large.
Corey Roth blog: www.dotnetmafia.com twitter: twitter.com/coreyroth - I hope you have planned as per MS recommendations? If not look into this before making any further changes: http://technet.microsoft.com/en-us/library/cc262787.aspx#section3
Document
5 million per library
You can create very large document libraries by nesting folders, using standard views and site hierarchy. This value may vary depending on how documents and folders are organized, and by the type and size of documents stored.
Library
Pryank Rohilla MCTS, MCAD - Hello,
Thank you for your responses. Yes i'm aware of Microsoft recommendations, in particular:
http://technet.microsoft.com/en-us/library/cc262787.aspx
I'm worried about the 100gb per content DB, even if it is possible to have 5000000 documents in a single library, if each doc occupies 1Mb we are talking about 5Tb of information, i don't think this is recommended..
I have a single DocLib and i'm thinking on splitting it into several Site Collections below the Root Site collection, with one DocLib inside each SC (equal to the one i have right now) this architecture seems a bit odd, since i'm spwaning site collections (probably about 30 SCs each with a content DB) only to distribute documents that are completely similiar in terms of metadata, but the site collection limit recomended by Microsoft per WebApplication is also very high (150000) they must have though on some very large implementations with SCs too...
And the only way i found for having separate content DBs is by using Site Collections. What is your opinion? should this limit (100GB) be ignored, is it ok to have several Gb on a single list? i haven't found a direct answer for this :(
best regards,
jv
João Vilela - Exceeding 100GB isn't necessarily going to break anything as you are aware. I know of installations that have content DBs twice that size and things seem to work ok. Is it recommended, probably not, but they get by. On the other hand, I know other admins that swear by never letting the db exceed 50 GB as well. I would probably do my best to try and stick to the published recommendations.
Corey Roth blog: www.dotnetmafia.com twitter: twitter.com/coreyroth- Marked As Answer byGuYumingMSFT, ModeratorTuesday, November 10, 2009 1:18 AM
- Unfortunately, there is no single recommendation Microsoft can make that caters to all possible scenarios working acceptably and performantly. However, the published document(s) which lend to the 100GB recommended size are what we feel to be acceptable for a wide range of scenarios.
For what it's worth, scaling across content databases is the best you will get when it comes to performance -- but as you can also appreciate it comes with added administration overhead; in this case splitting up your document library.
List size is more related to (doesn't mean it's not related, but less so) rows in your content database, rather than the size of the data itself, in fact this becomes even more apparent in SharePoint 2010. So I'm comfortable saying yes you can have 100GB in one content database -- at the same time, also look at this from the perspective of other admin tasks like Backup/Restore. Particularly if you're reaching 5TB of data storage in a content database, I have to say Backup-Resotre will be quite a task.
I wouldn't go the SC route really, the max recommended number there is largely relevant for the Profile and MySites feature -- plus if it doesn't make logical or semantic sense for your data to be organized that way, don't do it!- Marked As Answer byGuYumingMSFT, ModeratorTuesday, November 10, 2009 1:14 AM
