Follow PFE on Facebook
There is a lot of interest in the ability of SharePoint 2010 to use the new Remote Blob Storage (RBS) capabilities of SQL 2008 R2. Much of it good... some of it bad. The main issue is that many people are under some false assumptions about what RBS does and what it's actual benefits/trade-offs might be.
First, RBS provides a few clear and potentially valuable direct benefits:
That's it. That's what RBS gets you. When discussing a system like SharePoint, which has a heavy focus on file (BLOB) management, these can be fairly significant benefits.
However, these benefits come at a significant price. Specifically:
So, should you use RBS? Maybe, maybe not. If you're clear about the problem you're trying to solve and you clearly understand how RBS fits into solving that problem, then RBS may be a good solution. For example, if all of the following items are true, then you might consider RBS:
If ANY of the above items are not true... ANY OF THEM... then you should NOT be considering RBS.
Now... the true/false, fact/myth part of the conversation...
Finally, if you're still considering RBS or just want more information about it, a recently released whitepaper provides the most exhaustive and informative description of RBS I've seen to date. I strongly suggest reading it.
Note: This article has been updated to reflect the latest guidance from the SharePoint Product Group. Some artifacts may remain that reflect information prior to this update. If so, please leave a note in the comments for invesgitation and response.