May 19, 2011 at 3:53 pm
PLATFORM: SQL 2008 R2 Enterprise 64
ENVIROMENT: SHAREPOINT 2010 Enterprise
THE SCENARIO: A new SQL Instance will host a single database that is the storage for a SharePoint site that will be for document management & storage. No other DB will be on this same SQL Server and the SharePoint site that uses that DB will be for document storage and retrieval only; pics and scanned documents stored as anything from pdf to doc/docx and other Office file formats.
THE QUESTION: Should a site DB for SharePoint 2010 that will server to store nothing but documents be implemented using the Remote Blob Storage option for SharePoint/SQL Server or stored natively in the DB like all other Sharepoint DB's work?
My take on this, you don’t store BLOB data in a database. The counterpoint from the IT guys is why not store the docs in the DB since the DB and the server its on will be for notheing else but document storage and therefore perforamce is not an issue. My boss says that the Remote Blob Storage option has a lot of headaches and complexity itself so why mess with it when we don't care about performance for this DB?
Anyone here have experience with SharePoint 2010 specifically with this kind of scenario (large amount of document storage) using the DB for large amounts of BLOB Storage? Any gotchas with storing BLOB data in the DB even if performance is not a factor? I can’t help but think that even though the DB does not need to be fast it will still be prone to other management headaches by trying to store all those docs in one DB.
We are projecting an initial growth (after all existing docs are scanned and stored) of between 500GB and 1TB.
Any and all feedback is as always appreciated and I hope someone out there with SharePoint experience can provide some personal take on this same issue.
Kindest Regards,
Just say No to Facebook!August 8, 2011 at 5:30 pm
Wondering if you were able to get a response/ guidance? I have some similar requirements and was wondering the pros and cons myself.
Thanks!
August 10, 2011 at 3:08 pm
Sadly I haven't. That said there is some good news in this area. SharePoint has a new SP/Update coming out (may be out already ) that involves 'Content Scalability Support Changes'. You can get the full story at the below URL.
If you should happen to get any additional info on this please share in this post. It seems like the amount of resources for (SQL Server + Sharepoint ) for VLDBs is slim. When you add DPM to this it gets even slimmer.
Some of the changes mentioned in the blog include:
In short, the following supported limits were announced:
• Content databases of 200GB or less continue to be supported fully with out-of-box tools and functionality of SharePoint
• Content databases hosting document archives are supported with no limit to the size, other than that imposed by SQL Server itself
• Content databases hosting all other scenarios—loosely, “collaboration” scenarios—are supported up to 4TB
• A content database is supported up to 60 million items, including documents and list items. The supported limit for items in a single list or library (30 million) is unchanged.
• Size limits described above apply to the total size of data and content whether BLOBs are externalized using Remote BLOB Store (RBS) or not.
Kindest Regards,
Just say No to Facebook!Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply