10.3 Overview of Deployment Sizing 195
Chapter 10
documentation, installation package, and functional description will prepare
the operations and support groups for deployment and end-user queries, and
these should therefore be required for all add-on Web Parts in an enterprise
deployment.
In a larger deployment with multiple servers running SharePoint, ver-
sion control on all aspects of the deployment (including Web Parts) prevents
servers going out of sync and thus risking issues with incompatible software
versions or bug fixes that have only been installed on part of the overall
deployment. Perhaps the main challenge with add-on Web Parts is support—
more precisely, the question “who do I call in case of problems.” Contracted
custom development might not include a support agreement, which could
possibly put the operations team in a difficult position when troubleshooting
issues that might have something to do with custom Web Parts.
Even if the source code was provided as part of the submission, debug-
ging someone else’s code without knowing exactly what to look for is a night-
mare for any developer. It is imperative that a clear support and change
management responsibility is established before going into production with
add-on functionality. When possible for in-house or contract-developed
code, a business group or another entity should be assigned as the primary
owner instead of the original developer, since people come and go and Web
Parts might therefore be left orphaned.
10.3 Overview of Deployment Sizing
No doubt, one of the most important parts of planning a SharePoint deploy-
ment is getting nitty-gritty with the physical hardware. The days of simply
getting the biggest box out there in hopes of having it run the solution some-
what smoothly are long gone, and nowadays estimating the application
workload, turning it into meaningful numbers, and selecting a hardware
architecture that will perform the job to specifications with room for growth
has turned into an art form. Power consumption, cooling requirements, and
data center real estate are foremost on the minds of most architects when
they size applications for deployment; this is a change from the past, when
such things never even made it to the equation.
In this section, we look into the art form of server sizing and give you
the tools you require to make the best possible choice for your deployment.
While we touch on the add-on services and products of the Microsoft Office
System, it should be noted that the content is focused on Windows Share-
Point Services and SharePoint Server 2007 capacity planning.
In traditional client-server applications, such as Microsoft Exchange,
emphasis for server sizing is on the number of users and type of clients they
are using. Typically, the types of actions users are able to perform are limited

Get Microsoft SharePoint 2007 Technologies now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.