More often I’m hearing about SharePoint deployments with performance problems and recently one that is crashing! These aren’t my projects of course ;)
During a call with the client I was shocked to hear the consultant state that SharePoint was a black box – SQL maintenance wasn’t an issue. Hmmm…the last I heard SharePoint was a N-Tiered .Net/SQL application.
The problem? SQL Server…poorly maintained and architected. The solution? Get a DBA and an Architect that knows what they are doing – knows service management and capacity planning etc.
- SharePoint Administration Tool Kit x86 – http://www.microsoft.com/downloads/details.aspx?FamilyId=263CD480-F6EB-4FA3-9F2E-2D47618505F2&displaylang=en
- SharePoint Administration Tool Kit x64 –http://www.microsoft.com/downloads/details.aspx?FamilyId=F8EEA8F0-FA30-4C10-ABC9-217EEACEC9CE&displaylang=en
- Database maintenance guide – http://go.microsoft.com/fwlink/?LinkId=111531&clcid=0x409
- SharePoint Operations Manual – http://www.microsoft.com/downloads/details.aspx?displaylang=en&familyid=b91ce500-4ab7-4e1d-ac57-03b5d0e1ab8a
As you read the links you will discover that SharePoint uses Clustered Indexes which DBAs know become a performance hinderance in large environments. Why? Inserts and deletes fragment the Indexes and performance goes down hill. Also listed that grow out of control will eventually lead to slow downs farm wide an SQL locks and blocks.