Not So Random Thoughts...

A client recently inquired about leveraging SharePoint as a tool for storing large, multimedia files to create a “brand portal”.  I cautioned him of some of the limitations of SharePoint but also offered some additional insight into the possibilities.  I referenced a variety of other, more in-depth posts if you are interested:

SharePoint 2007 (MOSS): 

• Not a great product for storing larger multimedia files due to the significant overhead SharePoint places on files stored (e.g. – a 1 MB file stored on your hard drive can require as much as 2 MB of space when stored within SharePoint) within the SharePoint content database(s).  Microsoft does not recommend having content bases large than 100 GB and larger multimedia files would quickly take up that space.
• Out of the box, MOSS does not offer a mechanism for front-ending external blob storage (e.g. – file system, traditional DBMS, etc.) without significant custom development (requires Service Pack 1 or later – ISPExternalBinaryProvider) or the use of third party add-on such as StoragePoint or Open Text Storage Services for Microsoft SharePoint.
• I understand that implementing blob storage in a MOSS environment to be incredibly complex undertaking regardless if custom developed or if leveraging a third-party solution.
• Take a look at this blog for some additional insight as it relates to the SharePoint 2007 and external blob storage:

http://blogs.technet.com/b/vedant/archive/2009/06/17/external-blob-storage-in-sharepoint-2007.aspx

SharePoint 2010: 

• SharePoint 2010 does have support for blob storage via Remote Blob Storage (RBS - a set of standardized APIs that allow storage/retrieval of BLOBs outside of your main SQL database where a dedicated BLOB store is desirable for various reasons) in conjunction with SQL Server 2008 R2. 
• Since you are interfacing with an API, you are still looking at some level of custom development.
• Take a look at this FAQ about SharePoint 2010 Remote Blob Storage (RBS):

• There are concerns about the use of RBS including operational costs, operations efficiencies, the need for a third party Blob store, etc.  Take a look at this blog for additional information:

http://nevertalkwhenyoucannod.typepad.com/nevertalk/2009/10/externalizing-blob-storage-in-sharepoint-2010.html 

 Finally, I will leave you with this quote from Joel Olsen, the former SharePoint guru at Microsoft IT, who is still heavily involved with the SharePoint product and product team:

http://www.sharepointjoel.com/Lists/Posts/Post.aspx?List=0cd1a63d-183c-4fc2-8320-ba5369008acb&ID=328 

“Large Media Media itself has taken a turn in SharePoint 2010.  With the silverlight webpart and support for streaming media straight from document libraries, SharePoint 2010 takes a leap forward in support for media.  If you were to analyze youtube.com you’d find that the maximum upload is 10 minutes or 100MB.  I think that’s totally acceptable for SharePoint 2010 and with the large list enhancements and RBS you’ll find SharePoint as digital asset management more and more common.  Note the 2GB limit mentioned above.  For feasibility I still think it’s a bit crazy to store more than a few hundred MB in SharePoint databases, but RBS enhancements SQL 2008 R2 with third party do make me consider exceptions of up to 1GB.

I still don’t think you should dump most Training CDs or Product or that kind of media to SharePoint.  Most are still designed to run from the file system.

Improvements: Streaming media support, silverlight webpart for media, better image and thumbnail support, better all around digital asset management including remote blob storage considerations with third party vendors with SQL 2008 R2 (I don’t recommend using the SharePoint 2007 SP2 API)”

I would be curious to see if anyone out there has leveraged SharePoint for implementing a “brand portal” to learn more.