Archive for the ‘SharePoint Planning’ Category

SharePoint Database Sizing – a request for information

September 2, 2009 Leave a comment

When planning a deployment, one of the fundamental issues that needs to be addressed is providing sufficient capacity to accommodate the anticipated growth of the SharePoint environment. Microsoft provides some detail on best practices for capacity planning and management for SharePoint, mostly focussed on content or search database sizing and the effect upon performance.

Information on the size of SharePoint configuration databases is however decidedly thin on the ground. The second of the TechNet articles linked above lists the configuration database as being around 1.5 GB in size and states that the “configuration database will generally not grow past this size” although this is “not a hard limit”.

So this begs the question: just how large can the configuration database get? And how about the other supporting databases such as the Central Admininstration (SharePoint_AdminContent) and SSP database (SharedServices1_DB)?

And for the answer to this I’m turning to you good readers. Please vote to indicate the size of your configuration and other supporting databases so that we can all benefit from being better able to plan for the growth of SharePoint. If you have some interesting findings you’d like to share, please leave a comment.


Are we there yet?

You need to know what you want to achieve before you can claim to have achieved it.

Lately I’ve been reading a lot of Paul Culmsee’s insightful blogging at CleverWorkarounds and in particular his series focussed on the importance of shared understanding in preventing SharePoint projects from failing.

This has all come from advising on SharePoint development recommendations which transformed into providing detail on more general SharePoint governance that then metamorphosed into attempting to define the business requirements for implementing SharePoint in the first place. I’d liken the experience to taking a series of steps backward to gain a wider view of an sculpture only to discover that you’ve inadvertently left the art gallery.

The real problem is that currently there are no clear business requirements and little awareness throughout the organisation about the potential benefits. This threatens to result in other, more business critical, projects venturing down paths that don’t lend themselves to SharePoint integration at a later date.

This is something of a journey of discovery beyond that of the normal technical nature of this blog but if I can glean anything of value for other developers/architects then I’ll carry on posting on this theme.

Categories: SharePoint Planning Tags: