Friday, 15 August 2008

SUGUK Session - August 2008

The SUGUK session was the largest to date with 140 attendees, I thought it was an excellent session and Eric's presentation of performance considerations when coding was awesome, I picked up some useful stuff that I wish some of my dev's were there to hear ;)


My presentation on SharePoint Extranets seemed to be well received, and certainly kicked off some stimulating debate in the Duke of York afterwards!


I didn't manage to answer all questions (due to time constraints) but will keep my eye on the SUGUK forums (I would suggest either the Admin forum: or the Deployment one: for anything arising.


There were several requests for my deck, this is available here:

Get Adobe Reader (required to open PDF files)

Sunday, 3 August 2008

Content DB's - clearing up some confusion

Just thought I would qualify something, as I have been asked this a few times of late, and sometimes by people whom I would have expected to have understood this...


Within SharePoint (v2 or v3) the lowest ratio of content DB’s to Web Applications (virtual servers in v2) is 1:1

  • You have multiple content DB’s for a given web application.
  • You can have multiple site collections in a web application.
  • The lowest ratio of content DB’s to site collections is 1:1
  • You can have multiple site collections in a given content DB (recommended max is 50k – performance drops off after 50k, it isn’t a hard limit)
  • By default you only get 1 content db when you create a web application, you can add more from http://sca:port/_admin/cntdbadm.aspx (SCA > AppMan > Content DB’s) or from STSADM.


Where you have multiple content DB’s for a given web application, SharePoint will distribute site collections across the content DB’s.


Let’s say you had 3 content DB’s for a web application (DB1, DB2 and DB3).


The first site (say a Portal/Intranet at root) will go into DB1.


When you create new site collections (these must be collections NOT sub-sites/webs of the “root” Portal) they are distributed (round robin style) to the other content DB’s based on the order of priority (basically the order the content DB’s were created in) and by the number of sites in the content DB’s.

So, “site-A” goes into DB2, “site-B” goes into DB3, “site-C” goes into DB1, “site-D” goes into DB2, round and round we go (like a card dealer!).


The logic is not present to distribute site collections based on any attribute (URL path, metadata etc) or size.


You could end up in a situation where you have multiple contents DB’s (say 3) but due to bad luck all the large collab spaces end up in DB1. Therefore you will have a even distribution (numerically) of site collections across the content DB’s but DB1 will be huge while DB2 and DB3 will be small.