Arizona SharePoint Professionals Group JANUARY 31ST 2008Inaugural meeting
Agenda Group Overview Community News What's to Come Molding MOSS SharePoint Topologies Tonight’s Raffle
AZSPG Vision Free resource for the purpose of exchanging ideas and information related to Microsoft Office SharePoint Server 2007 and related technologies. AZSPG topics are of interest to Application Developers, Business Information Workers and System Engineers
Volunteers Needs Speakers Subject Matter Experts Sponsor Coordination Meeting Coordination Web Site Maintenance Graphics Invite Creation
Community News SP1 Released Office Developer Conference 2008 (2-10-08) Office SharePoint Conference 2008 (3-3-08) STSDEV Released TechEd (6-10-08) SharePoint Academy Class Discounts Available SharePoint Group IT Pro Survey Next AZSPG - 2-28-08
February Meeting • Community News • Deployment Panel Discussion • Discussion of real-world deployment challenges and solutions • Volunteers encouraged to be part of the panel and discuss real challenges – See Tim to signup • What You Need to Know About Governance and Customization Management • Heads-up on Windows 2008 & WSS 3.0
March Meeting Community News How to do team development with TFS, WSS, MOSS & Visual Studio Search Server 2008 and MOSS Search Enhancement Pack Rapid-Fire for Five – 5 Tips and Tricks from the field
Tonight’s Raffle Fill out your evaluations and tear off the bottom raffle number during the break or at the end of the night… Feedback is critical…Tell us what you think!
Doug Perkes – Consultant, Microsoft Services Molding SharePoint
Agenda SharePoint Capabilities—what exactly is SharePoint? Tooling—how did they do that?
SharePoint Plastic “SharePoint isn't a credit card, but it does mold very well. Not sure if it's play dough or plastic…SharePoint is a business productivity platform…If you can save 200 million dollars by using SharePoint it's that it is plastic and can fit to your needs. You simply need to understand what needs to be done (basically what the mold looks like) so that you can warm up the plastic to match.” --Joel Oleson
What can be done with SharePoint? Key Capabilities: Collaboration Social Computing Portals Enterprise Search Enterprise Content Management Business Processes and Forms Business Intelligence
Administrative Tools System Center Capacity Planner 2007 (http://shrinkster.com/u7o) Microsoft Virtual PC (http://www.microsoft.com/virtualpc) Application Pool Recycler (http://shrinkster.com/o9o)
Customization Tools SharePoint UI and Central Administration SharePoint Designer (http://shrinkster.com/u7p) MSDN Visual How-To’s (http://shrinkster.com/u7r) MOSS Query Tool (http://shrinkster.com/o9s)
Development Tools Visual Studio .NET 2005/2008 (http://shrinkster.com/u7n) STSDEV: Simple Tools for SharePoint 2007 Development (http://codeplex.com/stsdev) Andrew Connell’s Custom STSADM commands—GenSiteColumnsXml & GenContentTypesXml (http://shrinkster.com/ub8)
Call to Action Create your own Virtual PC image with MOSS Watch the MSDN Visual How-To’s Participate in the community, attend more AZ SharePoint Pros meetings Give us your feedback—what do you want to see & learn?
SharePoint Topologies Tom Wisnowski Sr. Consultant, Microsoft Consulting Services firstname.lastname@example.org
Pop Quiz! Forget the old definitions! They do not apply to Microsoft Office SharePoint Server 2007 topologies. • What is the Microsoft supported definition of: • Small Farm? • Medium Farm? • Large Farm?
Considerations when planning your physical topology Availability Capacity Performance Organizational requirements Differing availability requirements / SLAs Regulatory / data segregation requirements Functional requirements Licensing Cost
Topology Design Components Increasing complexity and cost
Getting started… • Review the TechNet planning guides • Plan for system requirements • http://technet2.microsoft.com/Office/en-us/library/0ed0b44c-d60d-4b85-87de-19065d9688351033.mspx?mfr=true • Design server farms and topologies • http://technet2.microsoft.com/Office/en-us/library/0ed0b44c-d60d-4b85-87de-19065d9688351033.mspx?mfr=true • Plan for performance and capacity • http://technet2.microsoft.com/Office/en-us/library/0ed0b44c-d60d-4b85-87de-19065d9688351033.mspx?mfr=true • Logical architecture components • http://technet2.microsoft.com/Office/en-us/library/0ed0b44c-d60d-4b85-87de-19065d9688351033.mspx?mfr=true
Getting started… • Document customer base • # users, usage profiles, locations • Gather requirements • Functionality • Availability • Plan for capacity • Plan for performance • Research and document design constraints
Logical Components SharePoint Topology Planning
Lists and Libraries • Can contain up to 5 million items • Split content up using folders • Try to not have more than 2000 items/folders at any one level in the hierarchy • Not a hard limit • Utilize indexed columns and custom views • Consider • Usability • Search Relevance • Size of the content database
Sites and Site Collections • 250,000 sites per collection / 50,000 collections per web application • Nest sites to reach 250,000 (2000 / level) • Site enumeration performance drops at 2000 sites • Consider • Usability & Search Relevance • Size of collection / content databases • Operations like export / import
Content Databases • Max size based on operations / SLAs • Most customers: 50GB – 250GB • Recommend no more than 100 per web application (based on SQL server spec) • Move to multiple SQL instances to increase • Try to group site collections of similar size and function into shared content databases • Site collections cannot span multiple DBs • Content deployment requires multiple DBs • STSADM can target content DBs / UI cannot* • New SP1 STSADM command “mergecontentdb” can be used to merge and split content dbs
Web Applications • 99 per Shared Service Provider • Consider server resources (10 per farm realistic) • 1-2GB memory typical • Sharing app pools can decrease utilization • 10 > will probably require multiple child farms • Consider • Top level URL requirements / SSL • Functional requirements (ex: self service site creation) • Process isolation
Shared Service Providers • 3 per farm, 20 max • Server resources are a big factor • Why multiple SSPs? • Differing functional requirements • Multiple administrative groups • Multiple index servers / multiple indexes * • In most scenarios, one SSP is all you need
Farms • No theoretical limit when isolated (running own SSP) • Consider CapEx/OpEx • Can consume a parent farm’s SSP or host an SSP for other farms to consume • 99 web apps per SSP apply • Can only share 1 SSP
Physical Components SharePoint Topology Planning