The document provides an overview of SharePoint 2010 site and database architecture, service applications, different SharePoint topologies, and prerequisites and steps for installing SharePoint. It discusses how SharePoint sites are organized hierarchically and have separate content, configuration, and other databases. It also explains how service applications in SharePoint 2010 are more independent than service silos in previous versions, and can be deployed separately. The document outlines hardware and software requirements and gives a high-level overview of installing SharePoint in single-server, small, medium, and large farm topologies.

1. Presented by
Narayana Reddy

2. Agenda•
• SharePoint 2010 Site & DB Architecture
• Service Applications
• Service Applications Vs. SSP
• SharePoint Server Types
• Different SharePoint Topologies & Limitations
• SharePoint Installation Pre-Requisites
• SharePoint Installation

3. SharePoint 2010 Site & DB
Architecture
• SharePoint has been designed in a layered way , to provide the ease in
Administrating the application
•There are different types of sites in SharePoint
•Central Administration Site
•Web Application
•Site Collection (Site)
•Site (Web)
•Databases Architecture
•Configuration Database
•Content Database
•Search Database
•Profile Database
•Others…

4. SharePoint Foundation is designed to scale out using a farm of front-end
Web servers
SharePoint 2010

5. SharePoint Foundation runtime loads into an IIS application pool
running ASP.NET 3.5
SharePoint 2010
SharePoint development environment using a single server farm

6. SharePoint 2010

7. SharePoint 2010
Web Application
Site Collection
Site Collection
Site Collection
Top Level Site(Root)
Top Level Site(Root)
Child Site Child Site
Top Level Site(Root)
Child Site Child Site
Child Site Child Site

8. Service Applications
•A Shared service is a component that does useful work. All Shared Service
components are considered part of the Shared Services framework. For
Example, Search is considered a shared service and profile is considered a
shared service
•Shared Services are the replacement to SSP’s and provide greater flexibility in
administering SharePoint. Shared Services have been built into WSS
framework unlike its predecessor, SSP’s, which were built into the MOSS
framework.
•In MOSS, the SSP was a one stop shop which contained several shared services
like search, profile, excel services for example. This in itself caused a multitude
of problems since it’s potentially a single point of failure for multiple services.
Also, SSP’s weren’t as flexible when providing specific permissions to manage
specific services within an SSP.
•SharePoint 2010 flattens an SSP so now each service is an independent entity.
This will make more sense after reviewing the entire blog.

9. Service Application vs. SSP

10. Service Application vs. SSP

11. SharePoint Server Types
SharePoint follows three tier architecture for greater performance &
load balancing.
Web Server
•Host Web pages, Web services,
and Web Parts that are
necessary to process requests
served by the farm.
• Direct requests to the
appropriate application servers.
• This role is necessary for farms
that include other SharePoint
Server 2010 capabilities. In
dedicated search service farms,
this role is not necessary
because Web servers at remote
farms contact query servers
directly.
• In small farms, this role can be
shared on a server with the
query component.
Application Server
Application server roles are
associated with services that
can be deployed to a physical
computer.
•Each service represents a
separate application service
that can potentially reside on
a dedicated application
server.
•Services with similar usage
and performance
characteristics can be
grouped on a server and
scaled out onto multiple
servers together.
Database server
In a small farm
environment, all
databases can be
deployed to a single
server. In larger
environments, group
databases by roles and
deploy these to multiple
database servers.

12. Different SharePoint Topologies &
Limitations
SharePoint can be installed in four topologies (Server Farms)
1. Single Server Installation (Stand Alone)
2. Small Server Farm
3. Medium Server Farm
4. Large Server Farm

13. SharePoint Hardware Requirements
Web & Application Servers
Component Minimum requirement
Processor 64-bit, four cores
RAM 4 GB (Development)
8 GB (Production)
Hard Disk 80 GB
Database Servers
Component Minimum requirement
Processor 64-bit, four cores (small deployments)
64-bit, eight cores (medium deployments)
RAM 8 GB (small deployments)
16 GB (medium deployments)
Hard Disk 80 GB

14. SharePoint Software Requirements
Software Requirement
Operating System
• Windows Server 2008 (64-bit) Standard, Enterprise, Data Center, or Web Server with
SP2
• Windows Server 2008 (64-bit) R2 Standard, Enterprise, Data Center, or Web Server
Database Server
• Microsoft SQL Server 2008 (64-bit) R2
• Microsoft SQL Server 2008 (64-bit) with Service Pack 1 and Cumulative Update 2
• The 64-bit edition of Microsoft SQL Server 2005 with Service Pack 3 (SP3).
Prerequisite Softwares which are
installed by preparation tool
• Web Server (IIS) Role
• Application Server role
• Microsoft .NET Framework version 3.5 SP1
• SQL Server 2008 Express with SP1
• Microsoft Sync Framework Runtime v1.0 (x64)
• Microsoft Filter Pack 2.0
• Microsoft Chart Controls for the Microsoft .NET Framework 3.5
• Windows Power Shell 2.0
• SQL Server 2008 Native Client
• Microsoft SQL Server 2008 Analysis Services ADOMD.NET
• ADO.NET Data Services Update for .NET Framework 3.5 SP1
• A hot fix for the .NET Framework 3.5 SP1 that provides a method to support token
authentication without transport security or message encryption in WCF.
• Windows Identity Foundation (WIF)
• Windows Update

15. SharePoint Installation
Practical Demonstration

16. Q & A