November 6-9, Seattle, WA SQL Server and SharePoint Best Frienemies Lisa Gardner Premier Field Engineer Microsoft

Who am I ? What is PFE? Lisa Gardner aka SQLGardner Production DBA for 13 years prior to joining Msft Working with SQL since 6.5 Premier Field Engineering Reactive and Proactive support for Premier customers Architecture/Project Guidance Team Mentoring Workshop Delivery Troubleshooting

Microsoft PASS 2012 Customer Stories From the Front Line Tues 11/6 8:30am-4:30pm Bob Ward Adam Saxton Pre-Con Breakout Sessions Inside SQLOS 2012 DBA-500-HD in Wed 11/7 1:30-4:30pm Bob Ward SQL Server and SharePoint: Best Frienemies AD-310-C in 6E Wed 11/7 4:45-6pm Lisa Gardner Working with Claims and SQL Server BI Technologies BIA-401-C in 6E Fri 11/9 8:00-9:15am Adam Saxton Troubleshooting SQL Server 2012 Performance with Extended Events DBA-407-C in 301-TCC Fri 11/9 8:00-9:15am Rohit Nayak 4C-3 11/7 – 11/9 10am – 6pm Friday closes at 2pm Early Birds – 7am-8am

Table of Contents SharePoint Overview SharePoint Databases Configuration, Setup, and Maintenance What to Look Out For

November 6-9, Seattle, WA SharePoint Overview Understanding the Application.

SharePoint Glossary WFE Web Application Service Application Site Collection ULS Logs Timer Jobs

SharePoint Web Architecture Farm Web Application Site Collection SiteListItem

Key Attributes Web Application Different IIS Site Created on each WFE Isolates Content Provides authentication mechanism Site Collection Container of Sites Quotas Decentralized Content Administration Also serves as a site Site Permission Inheritance Can Share layout and data with other sites Can provide unique feature set from other sites

Service Applications Provides granular pieces of functionality Some can be tied to a specific server Offers scalability, load balancing, fault tolerance for most services Many to many relationship with web applications and service applications Each web application can have a unique set of service applications

Timer Jobs SharePoint equivalent to SQL Agent OWSTimer - Windows service for SharePoint 2010 at a predefined schedule Uses same logging infrastructure as web tier Includes Correlation IDs Jobs can be nested

SharePoint Internal Data

Logging Database Stores all SharePoint usage and health data ULS trace log data Event log data Blocking SQL Queries Crawl and Query Statistics Feature Usage Page Requests +More

Logging Database

ULS Logs

Correlation IDs Generated for every request Logged from the start of a request through to the end Useful for troubleshooting and tracing On error pages, ULS logs, Windows Logs, SQL Traces Web Front-End Server Application Server ~~~~~~~~~~ ~~~ 7d25d051-ca73-43…

November 6-9, Seattle, WA SharePoint Databases So Many Databases, So Little Time

Configuration & Admin Content Databases Farm Configuration Store Objects Table – Serialized Objects Binaries Table – Farm Solution Store SiteMap Table – Links a site into the configuration Content Database for Central Admin is a Content DB with very specific templates - considered to be an extension of the configuration database Backup and Recovery It is Supported to back up this database It is Not Supported to restore unless the farm is fully stopped when the backup is taken

Configuration & Admin Content Databases General Recommendations Default recovery model is Full but in most cases this database should be run in simple recovery mode Initial Data File Size: 2GB is appropriate for most situations Config databases are typically smaller and do not get much load Mirroring Supported to mirror within the farm (partner on same network as primary) Not Supported to mirror asynchronously or to log ship over WAN

Content Database Stores all site data in a site collection Site Metadata Web Part Pages Files uploaded to document libraries List Items Security Solutions It is supported to Mirror in Farm for High Availability It is supported to Mirror Asynchronously or Log Ship over WAN for disaster recovery General Recommendations Run in Full recovery mode only if the site data requires point in time restores

Content Database Schema Why SharePoint seems so crazy. Userdata table Namespace Table Container Tables IdQuotaOther Metadata Sites SiteIdIdUrlTitleScopeIdMetadata Webs WebIdIdTitleItemCountScopeIdFieldsMetadata AllLists Id SiteId DirName LeafName WebId ListId DoclibRowId Other Metadata ntext sql_variant int float bit Other metadata nvarchar datetime 1… …16~35 Url

Content Database Layout Can contain site collections Scale out at the db level and the instance level. Sizing Guidance <200GB Maintenance tasks stay manageable Makes db movement and DR easier Plan for 2 IOPs per GB data Can have 200GB-4TB if.25 IOPs per GB Size and load depends on the sites they contain Separate very active sites into different site collections/content dbs Can have 32,767 dbs per instance, but recommend 200 per instance as manageability can be an issue 300 DBs per Web Application

Service Application DBs Search Admin Crawl Property Profile Syncronization Social Tagging Web Analytics Reporting Staging LoggingBDCStateSecure Store Reporting Services Power Pivot Project Server Performance Point

Database Scale Out Guidance Search Content Logging Web Analytics Other Content Admin/ Content Content

November 6-9, Seattle, WA Configuration, Setup, and Maintenance

Planning for SharePoint Setup Allow the SharePoint installer to create databases Modify file sizes and growth settings Rename dbs to remove GUIDs SharePoint setup and admin accounts required roles: DB Creator Security Admin Can be removed for the setup account but will need to be added again for any further installs – not recommended Patching/Service packs Adding a new Service Application Add Service Application account logins Requires db_owner role in DB

Instance Configuration Follow general Best Practices for SQL Configuration Use Latin1_General_CI_AS_KS_WS collation Configure for heavy TempDB usage Multiple data files Data and log files separated/isolated Pre-size data files Set max degree of parallelism to 1 SharePoint overrides with MAXDOP Set max server memory and use Lock Pages In Mem Consider setting fill factor (%) to 80

Database Configuration Do not use Auto Shrink Set Auto Create/Update Statistics OFF (content dbs) Set Page Verify to Checksum Set Auto Grow sizes to MB not Percent Pre-size for growth Monitor utilization and grow manually!

Index Maintenance Index Maintenance is extremely important in SharePoint DMV Sys.dm_db_index_physical_stats can be used to report index fragmentation SharePoint 2007 by default would rebuild every index via a Timer Job SharePoint 2010 does a much better job at keeping index fragmentation in check It only rebuilds indexes that are fragmented Updates statistics

Health Analyzer Rules Index defragmentation and statistics maintenance address the following databases: Configuration databases Content databases User Profile: Profile databases User Profile: Social databases Web Analytics Reporting databases Web Analytics Staging databases Word Automation Services databases Search Property/Crawl databases These databases contain proc_DefragmentIndices Run daily

Health Analyzer Rules Cont’d Search Property database Proc_MSS_DefragSearchIndexes Run weekly Crawl database Proc_MSS_DefragGathererIndexes Manual Always report as fragmented Execute this rule after the first full crawl

Statistics Health Analyzer rules rebuild indexes and update statistics First drops auto created stats AutoUpdate, AutoCreate – off in SP 2010 by default Update manually when: Query execution times are slow After maintenance operations such as table truncation or a large batch insert/update/delete

Why is Index/Stats Maintenance So Important? GUIDs are used as clustered primary keys Random values = unpredictable insert pattern 16 bytes each Heavy insert/update activity These properties lead to rapid index fragmentation due to many page splits Fillfactor helps delay the inevitable but increases space usage SharePoint rebuilds indexes with fillfactor of 80

November 6-9, Seattle, WA What to Look Out For Common issues

New Content Databases Use DBA created content databases! SharePoint hard codes small file size and growth settings Automation Options: Powershell is a great option to allow SP Administrators to create dbs! Have a number of empty DBs already created Must Do’s Use Latin1_General_CI_AS_KS_WS collation Set appropriate recovery model for your recovery needs Add SP farm setup account and service account with db_owner role

Full Crawl Impact When a full crawl is running – it is a very intensive operation that can have an impact on other dbs hosted on that instance – if asked about overall performance slowdown, ask if a crawl is running It is common to see deadlocking in the Crawl database during this time. If size rapidly grows: ask about the depth of crawling links in documents

Ensure Index Maintenance is Running Health Analyzer Rule Definition Databases used by SharePoint have fragmented indices Databases used by SharePoint have outdated index statistics Health Analysis Job in Logging DB Details in ULS logs

Excessive Blocking Common scenario: “The SQL Server is slow” Ask for ULS Log info Blocking/Deadlocks can be common in content DBs Try a manual update stats Inquire about large lists, dbs over threshold, and other capacity limitations being exceeded Ask about list throttling and “happy hour” Read Committed Snapshot Isolation is not supported

Others ASYNC_NETWORK_IO_WAITS Disk IO TempDB Bottleneck Very Large Queries Logging is the ONLY DB to be queried directly

Helpful Links Know the Limits! More info on SharePoint DBs

November 6-9, Seattle, WA Questions? Don’t forget to fill out evals!

November 6-9, Seattle, WA Thank you for attending this session and the 2012 PASS Summit in Seattle