Premium Content

Access "SharePoint performance sinks, swims with SQL Server throughput "

Don Jones, Contributor Published: 13 Oct 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 documents back on the NTFS file system... Access >>>

Access TechTarget
Premium Content for Free.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

What's Inside

Features

More Premium Content Accessible For Free