Introduction to SharePoint for SQLserver DBAs
2 likes480 views
The document is a presentation by Steve Knutson on managing SharePoint for SQL Server DBAs, covering SharePoint architecture, databases, backup and recovery, and maintenance best practices. Key topics include capacity planning, performance monitoring, and the importance of using SQL aliases and multiple content databases for scaling. It emphasizes understanding the unique environment and planning for growth, recovery options, and effective database maintenance.
![Temp DB
• Put on the fastest storage
• Use a dedicated LUN if possible
• Use “MB” rather than “%” auto-grow
• TempDB size = [MAX DB SIZE (KB)] X [0.25] / [No. CORES] = DATA FILE
SIZE (KB)](https://image.slidesharecdn.com/sqlsat614sharepointfordbas-170527025818/85/Introduction-to-SharePoint-for-SQLserver-DBAs-9-320.jpg)
Introduction to SharePoint for SQLserver DBAs
- 1. Intro to SharePoint for SQL Server DBA’s Steve Knutson | Microsoft MVP Office Servers and Services Stratos Technology Partners Managing Director #614 SQL Saturday South Island
- 2. Who am I? steve@stp.co.nz | @nztechtweet
- 3. Agenda • A bit about SharePoint Architecture • SharePoint Databases • How big, how many and how fast? • Backup Recovery • Maintenance do’s and don’ts • If you only remember a few things
- 4. SharePoint Architecture 101 SharePoint Server (Web and App roles) SQL Server Services ContentConfig Suitable for: • Dev and UAT • Small Farms
- 5. Or this… SharePoint Server (App roles) SQL Server Services ContentConfig SharePoint Server (Web roles)
- 6. Or this! SharePoint Server (App roles) SQL Server (cluster) Services ContentConfig SharePoint Server (Web roles) SharePoint Server (App roles) SharePoint Server (Web roles)
- 7. What are all these databases for? SharePoint has databases for three purposes • Farm configuration – contains the configuration of the entire SharePoint farm • Service Applications – configuration and data for SharePoint application services e.g. Search, User Profile, Managed Metadata etc • Content databases – contains user data e.g. site configuration and data
- 8. A transaction is a document SharePoint workloads are different in several ways • Content databases can contain documents. An “HTTP Get” from SharePoint can return a document (they can be big!) • Read to Write ratios can vary – rule of thumb 80% read, 20% write • A ‘Full’ Search Crawl will read every item and document in the Content Databases, generating high I/O in SQL.
- 9. Temp DB • Put on the fastest storage • Use a dedicated LUN if possible • Use “MB” rather than “%” auto-grow • TempDB size = [MAX DB SIZE (KB)] X [0.25] / [No. CORES] = DATA FILE SIZE (KB)
- 10. Capacity Planning • Soft limits (there are no hard limits) • 50,000 site collections per content db • 1TB per content db (but smaller is recommended) • 8 Web Front Ends per SQL server • Understand the size and growth profile of content • Versioning requirements • High growth vs archival • Access frequency • 80% Read, 20% write
- 11. SQL Server Memory, Disk and Network • RAM – Minimum 4GB (Dev), Good 8-16GB, Better >16GB • CPU cache - >2MB L2 Cache • CPU cores – Good 4 cores, Better >4 cores • Disk latency – Good < 10msec, Better <10msec (Data) <5msec (Tlog) • Network latency (SQL to SP server) – Less than 1ms
- 12. SQL and SharePoint Server Config • Keep up to date with patches but confirm SP supported version • Use a dedicated SQL server if possible • Plan your content databases and “scale out” if necessary • Use SQL Aliases
- 13. Content Databases • Using dedicated content databases per site collection allows you to recover individual site collections and other management flexibility • This is important for recovery and DR
- 14. Remote BLOB Storage • Has some limitations • No encryption or compression • Best for… • Few large BLOBs (mostly read access) • Worst for… • Lots of smaller BLOBs (or intensive write access) • Requires Enterprise licensing • Third-party add-ons make this much better • Adds complexity
- 15. Business Data Connectivity • Can present SQL views / tables in SharePoint • Can write data back into SQL SharePoint also supports oData and REST • Use SSIS to pull data from lists (on-premises & cloud)
- 16. Access Services • Access databases published to SharePoint • Uses SQL to host tables NOT Access • NB: Access Services is end of life for SharePoint Online
- 17. Business Intelligence Services (on-premises) • PowerPivot • PerformancePoint • SQL Server Reporting Services Cloud • PowerBI (Pro license)
- 18. Secure Store • Manages credentials for BI Services • Works with Microsoft and non-Microsoft data sources • Authentication: • Pass-through (logged in user) • Data access account • Non-windows accounts • Reduces need for Kerberos (but isn't a complete replacement)
- 19. Which Recovery model? Microsoft recommend using both the Simple and Full recovery models. Full Model for these databases • Configuration, Admin Content, Content, Secure Store, BDC and PerformancePoint Simple Model for these databases: • Search and User Profile Service
- 20. Backup and Restore • Understand what you might need to recover • Library, List, File or list item • Site • Site Collection • Web application • Farm • Use the recycle bins first • Unattached database recovery • Get sign-off on your RTO and RPO’s, don’t assume they are the same as other systems
- 21. Maintenance Indexes - Fragments happen! (who said by design?) • Performance degrades as fragmentation increases – more I/O • Content and Search DB’s are most susceptible • Use sys.dm_db_index_physical_stats, it is more accurate that DBCC Showconfig
- 22. Maintenance Do’s • Auto-defrag (Content Databases only) • Shrink content db’s (but not other database types) • Update statistics • Change the server wide fill factor to 70% • Use DBCC CheckDB to check for consistency errors • Check that your backups are working • Do maintenance during off-peak hours
- 23. Maintenance Don’ts • Use maintenance plans to shrink databases • Drop and recreate indexes! (definitely don’t do this…) • Shrink any databases other than Content DB’s • Auto-shrink databases • Run maintenance tasks like DBCC or index rebuilds during business hours • Directly update SharePoint databases!!!
- 24. Know your environment SharePoint is a platform with a great deal of flexibility and wide range of uses. Your environment will be unique, so take time to understand normal: • Setup performance counters • Monitor your environment doing Search Crawls • Be proactive about database growth • Prepare for bulk data migrations • Practice recovery scenarios
- 25. If you only remember a few things • Always use a SQL Alias for SharePoint • Use multiple content databases if you have lots of data (plan for scale) • You can scale out or scale up • Capacity Planning is important • Measure “YOUR” environment • Understand “YOUR” recovery options
- 26. Q & A time
- 27. SQL SATURDAY | #614 | South Island 2017 Steve Knutson | Microsoft MVP Please fill out your evaluation forms. You have them in your A4 pack from registration. Please put them in the box at the front of the room. There are spot prizes for completed evaluation forms.
- 28. SQL SATURDAY | #614 | South Island 2017 Steve Knutson | Microsoft MVP Please fill out your evaluation forms. You have them in your A4 pack from registration. Please put them in the box at the front of the room. There are spot prizes for completed evaluation forms.
- 29. Thank you to our sponsors: Gold Sponsors Silver Sponsors Bronze Sponsors