- 1. SQL and Storage Considerations for SharePoint Server 2010
2. About Mike
- Product Manager at Quest responsible for availability, scalability, and manageability.
- Previously instructor for the Microsoft Certified Master program on several topics including Backup/Restore, HA, and DR.
- Entrepreneur, Mad Scientist, and soon an Author.
- Previously at Microsoft. Went from support to designing some of Microsofts most critical services in just 5 years.
- U.S. Army before that. Computers, Finance, Accounting, andArmor (M1A2 Tank)
- Whats new in SharePoint 2010
5. Whats Changed in SharePoint 2010
- More functionality out of the box
- Bigger variety in workloads
- Harder to make recommendations
- Some lessons learned built in
6. SharePoint 2010: Bigger Than Ever! 7. But Wait! Theres More! 8. Services in SharePoint 2007 9. Services in SharePoint 2010 (a la carte) 10. 11. 12. Better Multi-TenancyIPSEC or SSL SSL 13. Tenant Admin Page 14. Database Mirroring Support
- Support for automatic failover using SQL mirroring high availability mode
- Leverage failover partners for each database you create
- Read more about how this works on my bloghttp://www.sharepointmadscientist.com/Lists/Posts/Post.aspx?ID=46
- No automatic provisioning
- No automatic failover using high protection mode
- Keep database mirroring best practices in mind. Less than 50 database per instances... since we already have so many, you can see that can be a problem.
15. Database Mirroring with SharePoint 2010 16. Database Mirroring in SharePoint 2010 17. Demo
- High Availability using Database Mirroring
18. Command & Control
- Throttling Tell end users to leave you alone. Your busy!
- Large List controls tell end users theyre crazy trying to make that query, but admins, no problem!
- SharePoint designer maybe not
- Developer Dashboard Learn just how bad your developers are.
- Sandboxing More like prison for unsavory code.
- SQL Resource Governor The nuclear option!
19. Turn on the Developer Dashboard
- C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14BIN>stsadm -o setproperty -pn developer-dashboard -pv ondemand
- Run Powershell from the start menu as administrator by right clicking.
- Execute a Dashboard.ps1 script file containing this:
- $ddSettings = [Microsoft.SharePoint.Administration.SPWebService]::ContentService.DeveloperDashboardSettings;
- $ddSettings.DisplayLevel = OnDemand;
- $ddSettings.RequiredPermissions =EmptyMask;
- $ddSettings.TraceEnabled = $true;
- Display Options = On, "Off" or "OnDemand"
20. Large List Controls Configurable List Throttling And Thresholds You control when and how much! List throttling controls forces end users to create more efficient views with < x number of items. 21. SQL Best Practices 22. SQL Health = SharePoint Health!
- Sub-optimal SQL perf will radiate to other components in the farm.
Database Management is Paramount! 23. Databases in SharePoint 2007 24. Databases in SharePoint 2010 25.
- Min & Max values = Total memory 2GB for OS overhead
- Allocate 1 data file per processor core
- Pregrow databases & never autogrow
- Use 64KB or larger multiple for RAID stripe size
Configure SQL to conform w/ best practices 26. Pregrow databases and never autogrow 27. Best Practices Analyzer Health Rules Runs on a Timer Job Create your own! Repair Auto-magically! 28. Demo
- SQL Best Practices using SharePoint Health Analyzer
- Virtual is never as good as physical (sharing)
- Some virtualization features dont work well
- E.g. Resource pool allocation aka overcommit
- Virtualization introduces some artificial limitations to scaling up
- Processor limitations per machine
- Ability to leverage memory
- Sharing across bottlenecks (hw bus, NIC)
- Some roles work better with virtualization than others
Virtualization is Great But Be Careful! 30. 31. Assign appropriate hardware to VMs Web App SQL Processor Minimum 2.5Ghz 2.5Ghz 1.4Ghz Recommended >3Ghz Dual >2.5Ghz Dual >2.0Ghz Best Practice 3.0 Ghz Quad 3.0Ghz Quad Dual 2.0 Quad Memory Minimum 2GB 2GB 512MB Recommended >2GB 4GB >2GB Best Practice 8GB 16GB 32GB 32. Storage Best Practices 33. Manage Storage Capacity 34. Allocate as many disks as needed to SQL Temp Logs Search Data 35. Think Disk IO! Not Disk Capacity! 36. Calculating Disk IO An Example 37. Best Practices SQL Disk IO
- Allocate separate and dedicated disks with the following specifications:
- * Raid 1 or variants (0+1, 1+0)
- ** Depends on type and amount of content being indexed
- *** 2000 IOPS minimum. Plan on 1500 IOPS per simultaneous crawl. (e.g. 3 crawls = 4500 IOPS)
- **** Use Raid 5 when redundancy needs are met with replication
38. Use RAID 10 39. Demo
- SharePoint 2010 = Xability
- SQL Optimization and Management is Paramount!
- & Storage Optimization too!
- SharePoint scales out well. Adjust SQL accordingly
41. Quest Solutions for SharePointSite Administrator for SharePointUnderstand, manage and secureyour SharePoint environment Migration Manager for SharePointSharePoint to SharePoint migration File Migrator for SharePointFile shares to SharePoint migration Recovery Manager for SharePoint Granular SharePoint recovery for enterprise-level needs
- Enable rapid developmentof SharePoint applications
Public Folder Migrator for SharePoint Exchange Public Folders to SharePoint migration Notes Migrator for SharePoint Notes application content to SharePoint migration Quest SQL Server SolutionsMaximize SQL Server performance while simplifying tasks and providing visibility and control