Access your Pro+ Content below.
SharePoint performance sinks, swims with SQL Server throughput
This article is part of the SharePoint Insider issue of August 2012
When things slow down in a SharePoint system, the initial fix is often to add more Web servers to better handle the load. But those front-end servers rely on the same back-end database server, and the back end is where SharePoint usually encounters the most performance problems. That’s because it essentially relies on SQL Server as both a database and a file system. It’s not that SQL Server isn’t a speed demon; it can be. But SharePoint’s processing demands tend to highlight SQL Server’s most common bottleneck: disk I/O. It’s important to keep that in mind when planning for long-term SharePoint performance management. So what can you do to mitigate, or even avoid, the logjams that can snarl SQL Server throughput? Start by getting SharePoint’s binary large objects, or blobs -- typically file attachments if you’re a SharePoint person -- out of the SQL Server database. Both SharePoint and SQL Server support Microsoft’s Remote BLOB Storage (RBS) technology, which enables SQL Server to put all of those Word, Excel and other ...
Access this PRO+ Content for Free!
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
Features in this issue
SharePoint 2010 collaboration can be beefed up with open source add-ons that offer organizations with tight budgets a leg up in addressing the shortcomings of the platform’s built-in capabilities.
A SharePoint farm backup as part of an enterprise SharePoint 2010 backup strategy is simple, but on its own might not be enough. Brien M. Posey points out the other important considerations.
To help ensure that SharePoint performance doesn’t get bogged down, organizations need to build and maintain a scalable back-end database system that can eliminate SQL Server disk I/O issues.