Tip #29. Why to split large collaboration site between different site collections

Rate this item
(0 votes)

SharePoint functionality is build on the top of SQL Server and has a tight cohesion with SQL Tables. Any user’s actions on the SharePoint site lead to the data entries manipulations across several tables. 
Unfortunately, SharePoint implemented in the way to have few large tables rather then several small tables, and it stores a lot of contents in one single table. Such approach has a side-effect in table locks, which might hinder the performance of SharePoint sites if you are not aware about such table-centric design

With this in mind, consider splitting the content of large Collaboration site between different Site Collections. The reason for this that Site Collection is implemented as a huge single table.

Let’s imagine that you have site collection with 200 sub-sites, and some of user’s action force the transaction in SQL Server. Such action will lock Site Collection table, thus all 200 sites will be locked as well. In this case all users can’t interact with the SharePoint and will be waiting when that action competes.

There is no workaround for this, and the only way to track such issue is checking how your SharePoint sites performs – it case number of locks your will see noticeable performance degradation. Monitor SQL locks against SharePoint tables, to find such cases.

Update: consider splitting your site collection to be less then 100Gb-150Gb, otherwise you will have lots of locks in site collection table. The best tools to split site collection and move content across contentDB is "SharePoint Administration Toolkit"

Leave a comment

Make sure you enter the (*) required information where indicated. HTML code is not allowed.