blog.eardley.org.uk SharePoint Databases What you need to know Alan Eardley SQL Saturday Exeter 25 April 2015

blog.eardley.org.uk Who Am I? Lead SharePoint Technical Architect at CPS Developer, DBA, Business Analyst, Project Manager, Architect SQL Server SharePoint 2003 – 2013 Office 365, Azure, Project Server/Online, Dynamics CRM

blog.eardley.org.uk What will I cover? What does it do? How does it work? How does it use SQL? What is SharePoint? How many databases does it need? How does it grow? HA & DR Planning Are there any pre-requisites? How do I help with the build? Roll-out This relates to on-premises SharePoint NOT Office 365

blog.eardley.org.uk SharePoint – What does it do? Document Management Content Management Process Management Search PublishingSocialCollaboration Business Intelligence

blog.eardley.org.uk SharePoint – How does it work? Lists & LibrariesSitesSite CollectionsWeb Applications Intranet Departments HR IT Documents Knowledge Base Help Desk Issues Sales Projects Upgrade to SP2013 Risks Issues Tasks Upgrade My Sites Client Extranet

blog.eardley.org.uk SharePoint – How does it work? Business Connectivity Services Managed Metadata Services Excel Services PerformancePoint Services PowerPivot for SharePoint Project ServerSearch User Profile Service

blog.eardley.org.uk SharePoint – How does it use SQL? Most Service Applications utilise at least one database Service Applications At least one database per Web Application Each site collection can have a database Content Databases Multiple Databases My Sites Databases should not exceed 200GB in size With the exception of Records Centre databases

blog.eardley.org.uk Planning – How many databases does it need? Types of Database –Administration –Content –Service Applications How many databases will be required? How large do they need to be? How fast will they grow?

blog.eardley.org.uk Admin & Content Databases Default Database NameLocationSizeInitial SizeGrowthRead/writeScaling SharePoint_Config Must be co-located with the Central Administration databaseSmall2GBLog files grow rapidly90/10Up SharePoint_AdminContent_ Must be located on the same database engine instance with the configuration databaseSmall1GB Will grow if PowerPivot for SharePoint is installed with default settings90/10Up WSS_ContentNone<200GBVaries Up or Out

blog.eardley.org.uk Service Applications Default Database NameLocationSize Initial SizeGrowth Read/writ eScaling Bdc_Service_DB_ NoneSmallVery slow90/10Up Managed Metadata Service Application_Metadata_ NoneMedium Growth factors include the amount of managed metadata80/20 Up per service application PerformancePoint Service _ NoneSmall1GBVery slow80/20 Up per service application DefaultPowerPivotServiceApplicatio nDB_ NoneSmallVery slow80/20Up only ProjectWebAppNone Small to MediumVery slow80/20 Up per web application

blog.eardley.org.uk Search Default Database NameLocationSize Initial SizeGrowthRead/writeScaling Search_Service_Application_DB_ The Administration database should fit into RAM on the server so that the server can handle the end-user query load most efficiently. Because of this requirement, it is usually best not to have the Administration and Crawl databases located on the same server.Medium10GB The factors that influence growth include the number of best bets, the number of content sources and crawl rules, the security descriptions for the corpus, and how much traffic.50/50Mostly Up Search_Service_Application_Analy ticsReportingStoreDB_ None Medium to Large Write-intensive during analytics update90/10 Scale out by creating additional Analytics Reporting database using a split operation when the main database becomes >200 GB. Search_Service_Application_Crawl StoreDB_ NoneMedium Depends on the growth of the document corpus90/10 Scale out by creating additional Crawl database per every 20 million items crawled. Search_Service_Application_LinkS toreDB_ We recommend that if you have sites that have heavy traffic, the Link database should use separate spindles from other databases Medium to Large The Link database grows on disk by 1 GB per 1 million documents fed. The click through data grows linearly with query traffic, 1 GB per million queries.30/70 Scale out by creating additional Link database per every 60 million documents crawled. Also add additional Link database per 100 million expected queries per year.

blog.eardley.org.uk Single Farm Web Front End Presentation Application Server Workflow Manager Office Web Apps Application SQL Server Data

blog.eardley.org.uk High Availability Mirroring –SharePoint supports mirroring Clustering –Preferable to mirroring as it is at server level Always On Availability Groups –Builds on the benefits of Clustering

blog.eardley.org.uk Backup As a DBA, same as any other application –Full backups –Differential backups –Transaction backups Check consistency Fragmentation –Check for index fragmentation –Check for drive fragmentation

blog.eardley.org.uk Recovery Overview Site Everyone 30 days Items and documents Automatically moved to site collection recycle bin Site Collection Site collection administrator First in – first out Includes sites

blog.eardley.org.uk Recovery When a site is required to be restored When a site collection has been deleted Content Databases When a Service application needs to rebuilt Service Application When a farm needs to be recovered Central Admin

blog.eardley.org.uk Shared Services SharePoint Service Applications –Search –User Profile –Managed Metadata –Secure Store –Business Connectivity

blog.eardley.org.uk Multiple Farms, Multiple Data Centres

blog.eardley.org.uk Data Level

blog.eardley.org.uk How Can I Help? Set up SQL Instance correctly Understand the database usage profiles Configuration Standards and processes PowerShell Installation Monitor Plan for growth Backup Maintenance

blog.eardley.org.uk Configuration Used a dedicated instance Default Collation - Latin1_General_CI_AS_KS_WS MAXDOP = 1 Disable auto-create statistics Define the maximum memory Make a note of the Port Number the Instance is listening on Single filegroup per DB

blog.eardley.org.uk Support The general rules to not invalidate Microsoft Support are: –Do not add anything to the SharePoint databases Stored Procedures Triggers Tables Indexes –Do not run frequent queries against the SharePoint Databases

blog.eardley.org.uk Summary The number of databases depends on the service applications The size of the databases will depend on –The number of users –The number of documents and the amount of content –The amount of usage of SharePoint A database instance for SharePoint has specific requirements HA and DR strategies are a combination of SharePoint and SQL approaches SharePoint databases are the same as any other databases

blog.eardley.org.uk SharePoint Database References blog.eardley.org.uk/2015/03/sharepoint-databases-knowledge-base/ A combination of Microsoft documentation –SQL based –SharePoint based Initial sizes Growth Usage HA/DR Links to PoSh to create the databaes

blog.eardley.org.uk Today is brought to you by and in association with

blog.eardley.org.uk Please visit our sponsors

blog.eardley.org.uk Thank-you Alan Eardley – Office 365 | SharePoint | Project Server | CRM | Recruitment