Name: Title: Company: Joel Oleson Sr. Architect Quest Software
Who is SharePoint Joel? 8 year SharePoint Veteran First SharePoint Admin! Sr. Technical Product Manager - SharePoint team Launch of SharePoint Server 2007 Top IT SharePoint Blog Blog: http://www.sharepointjoel.com Twitter: @joeloleson
Audience Poll SharePoint Admins? Less than 3 years in SharePoint? Belong to SharePoint &/or.net user groups?
SharePoint Best Practices: Architecture Fundamentals Core Logical Architecture Physical Architecture Designing Information Architecture Avoid Common Mistakes Microsoft Confidential
WSS 3.0 and SharePoint Server 2007 Web Forms, Excel Services, BDC SharePoint Server 2007 Enterprise MOSS FIS For Internet Sites & Enterprise Intranet Doc Management, Web Content Management, Search, & Portals SharePoint Server 2007 Standard Intranet/Extranet Standard Platform & Collaboration (blogs & wikis) Windows SharePoint Services 3.0 Windows Internet Connector Microsoft Confidential
IIS Web Sites = IIS Virtual Servers = Web Applications IIS WSS 2.0 / SPS 2003 WSS 3.0 / SharePoint Server Web Sites Virtual Servers Web Applications Physical Server Web Application(s) Top Level Site(s) Site Collections Site(s) Site Collection
Consistency in Hierarchy WSS 3.0 Web Applications Site Collections Sites Templates & Features MOSS 2007 Web Applications Site Collections Sites Templates & Features Microsoft Confidential
Servers Have Services are Are Roles Servers have Roles Web Front End (WFE) Query Calculation (Excel) Index (Non SharePoint) Database Server Simplified Really Just 3 Roles WFE/Query 99% Index (App Tier) SQL Note: Never put Query and Index on same server if there is another Query server! Microsoft Confidential
Key concepts 32 bit or 64bit binaries **Note: SharePoint 2010 requires 2008 64bit & 64bit SQL 2005 or 2008 Install Basic NOT RECOMMENDED except for POC Advanced Allows you to connect to SQL WFE only vs. Full install Language Packs (Downloads on the Web) WSS MOSS Ifilter packs Microsoft Confidential
All in One All SP Roles SQL WFE/ Query SQL Index WFE/Q uery SQL Microsoft Confidential
Performance Picking Your Topology 10 Server Farm (Large) User requests Load balances web front end servers 5 Server Farm (Medium) User requests Web front ends + application(s) Application(s) Index Query Query Calc + 2 Clustered SQL server Application servers 3 Server Farm (Small) User requests Clustered SQL server Each load-balanced server includes: Web front end Applications Dedicated SQL server Single Server User Requests One Server which contains: Web front end Application Database Availability
Usage # Users Solution (The answer before the question) Authentication Type (Anonymous vs. AD) Caching Offload devices Business & Tech Requirements Client & Server Performance Requirements SLAs (Uptime/High Availability Req.) WAN Considerations (Multi farm) Data GBs/TBs of data Total # Files and Items (rare) Microsoft Confidential
SharePoint in common LOLCATS.COM
You MUST learn the difference between site and site collection despite the confusion. Site = Web = Spweb aka subweb STSADM = Web UI=site Site Collection = SpSite STSADM = Site Central Admin = Site UI= Site Collection Microsoft Confidential
Defaults have Faults Server Basic Install (BAD!) All On C Drive No Backup Restore Complexity List and Site Collection All One site collection Not Configured: Quota, Expiration, Auditing, Versions, Workflows, Meta Data capture All items view default (flat) Database One database Db config (log and db location) No maintenance plan
What is the most scalable object in SharePoint? Site Collection Can I run WFE and Query on one box and WFE Query Index on another? NO! Is a default basic install good enough to get started? No! Is Virtualization and SharePoint ok? Yes! Microsoft Confidential
Microsoft Confidential
Containment Hierarchy * Farm Internet, Extranet, Intranet Servers Web Front End, APP, SQL * Web Applications Central Admin, SSP Admin, Content Databases Content, Config, SSP, Search * Site Collections Internet, Intranet Portal, Wikis, Blogs, Team, Doc, Meeting * Sites Wikis, Blogs, Team, Doc, Meeting Workspaces Lists Doc Lib, Pages, Events, Discussions, Surveys, etc Items Files, calendar items, contacts, customers, images, custom
Joel's Cheat Sheet for Hosting Dedicated Farm(s) Ideal for applications such as Project Server, Performance Point, BDC applications, CRM, Sales SAP/Siebel and Finance Solutions built on SharePoint Great for staged deployments i.e. dev, test, authoring to production Web App Ideal for point solutions, Records Management, for Legal Holds, department solutions, and groups of site collections Memory isolation and separate SSP such as Search Solutions Site Collection Support 100s-100K+ sites Ideal for Collaborative environments including intranets, Projects, extranets Document Management where scale is into +TBs Sites Information and aggregation Portals such as Intranets WCM Internet sites with page libraries
SharePoint Server Logical Model Service Offering Permanent Structured SharePoint Server Sites Central Portal Division Portals Permanent Central Portal Web Application Permanent Division Portals Web Applications or Site Collections Ad Hoc WSS Site Templates SharePoint Server Sites Groups & Teams Projects & Workspaces My Sites Semi Structured Consolidation on 1 to 3 Web Applications 1 Web App per Region
Unit TechNet Max Joel s Guideline Joel s MAX Web Apps per Farm 8 5 Content Webapps with 8GB RAM Databases per WebApp Site Collection per Web App Size per content database 16 app pools 100 web apps w/ 32GB RAM, 64 bit - 100 per SQL server 300 with 32GB RAM, 64 bit 50,000 100,0000 - - 100GB 1 TB with serious list and site optimization (advanced only) Size per Site Collection - 15GB in multi-tenant DB 100GB in dedicated DB 25GB in multi 1TB in dedicated Db Sites in Site 2000 100 500 Items per List 2000 items per view Use Custom Views and search UI for large lists It s pain tolerance
Plan your lists and libraries Throughput differences between flat document library vs. document library with folders Microsoft Confidential
#8 SharePoint Common Mistakes
Operations and IT Failures Server Poor configuration (Not planned - defaults) Insufficient RAM and Disk allocation Information Architecture Poor choice of Site vs. Site Collection Structure Flat Lists One Content Database Network Poor Network between WFEs and SQL No plan for WAN (User complaints without answers) Operational Backup/Restore No Backup Emergency: No Restore plan or steps Disaster Recovery More like Disaster
Be sure to PLAN your logical infrastructure & Physical Don t forget a Governance Plan! Where do you get your information? TechNet, MSDN, SharePoint Team Blog, SharePoint User Groups http://www.sharepointpros.org, and blogs!! Twitter? http://www.sharepointjoel.com @joeloleson Microsoft Confidential
Quest IT Solutions for SharePoint Quest SQL Server Solutions Maximize SQL Server performance while simplifying tasks and providing visibility and control Site Administrator for SharePoint Discover, understand and manage your SharePoint environment Quest Web Parts Enable rapid development of SharePoint applications Recovery Manager for SharePoint Granular SharePoint recovery for enterprise-level needs Migration Manager for SharePoint SharePoint 2003 to 2007 migration File Migrator for SharePoint File shares to SharePoint migration Public Folder Migrator for SharePoint Exchange Public Folders to SharePoint migration Notes Migrator for SharePoint Notes application content to SharePoint migration 33
SharePoint Exams! Get Certified on the New Exams!!! For IT Pros: 70-631 - Windows SharePoint Services 3.0 - Configuring 70-630 - Office SharePoint Server 2007 - Configuring For Developers: 70-541 - Microsoft Windows SharePoint Services 3.0 - Application Development 70-542 - Microsoft Office SharePoint Server 2007 - Application Development MCM and MCA!
Questions?