Databases That Support Sharepoint 2013

DATABASES THAT SUPPORT SHAREPOINT 2013

Co-location guidance: Whether a database must or must not be Scaling guidance: Recommended SQL Server edition: A specific edition of SQL Server Microsoft SQL Server databases are integral to SharePoint 2013. The databases used in a specific environment are determined by the product, Definitions located on the same server instance with another database.  Scale up: to increase the size available to the database, move to a that is recommended, and why. In general, in this poster, version, edition, and features that are running. Database size, and the edition of SQL Server that you run are determined by the capacity and larger server. recommendations are made based on the assumption that you are I/O patterns: Whether the database is mostly used for reading or  Scale out: to increase the size available to the database, add running an enterprise environment. feature requirements of your environment. writing data. another database. Multiple database icons indicate scale out. SHAREPOINT SHAREPOINT SERVICE APPLICATIONS SQL SERVER

SharePoint system databases SharePoint User Profile service databases (Server) SharePoint 2013 (Foundation and Server) SharePoint Server 2013 SQL Server 2008 R2 (SP1) & SQL Server 2012 service application databases service application databases system databases Configuration Profile (SharePoint_Config) (User Profile service application, App Management Project Server 2013 master Contains data about all SharePoint databases, all Internet Information User Profile Service Application_ProfileDB_) (App Management service application, (Project Server service application , ProjectWebApp) Records all system level information for a SQL Server instance, Small Services (IIS) Web sites or Web applications, trusted solutions, Web Stores and manages users and their social information. App_Management_) The database stores all the data for a single Project Web App (PWA) enabled including logins, configurations, and other databases. Medium - large Small Small Part Packages, site templates, and Web application and farm settings Scaling guidance: Scale up the database that supports the service Stores the App licenses and permissions that are downloaded from the Small - medium site, along with the following: Scaling guidance: Scale up. (Significant growth is unlikely). specific to SharePoint 2013, such as default quota and blocked file application instance. Global Marketplace.  All Project and Portfolio Management (PPM) data types. Scale-out by creating additional instances of the service application, Scaling guidance: Scale-out only on SharePoint Online  Time tracking and Timesheet data model Requirements: however, the decision to create a separate service application is likely to be I/O patterns: Write-heavy during Apps installation and license renewal.  Aggregated SharePoint project site data Used as the template for all databases created in an instance.  Must be co-located with Central Administration Content database based on business, rather than scale, requirements. Significant database growth is unlikely. Scaling guidance: Scale up. (Significant growth is unlikely). Small  Only one Configuration database is supported per farm. I/O patterns: Read-heavy Secure Store Service Scaling guidance: Scale up the SQL Server that hosts the Project Server Scaling guidance: Scale up only, significant growth is unlikely. service application databases. (Secure Store service application, msdb I/O patterns: Read-heavy Synchronization Secure_Store_Service_DB_) Records operators, and used by SQL Server Agent to schedule alerts (User Profile service application, Small Stores and maps credentials such as account names and passwords. and jobs. User Profile Service Application_SyncDB_) Co-location guidance: For secure credential storage, it is recommended that Small Scaling guidance: Scale up. (Significant growth is unlikely). Stores configuration and staging data for use when profile data is being Medium - large the secure store database be hosted on a separate database instance with SQL Server PowerPivot Service Application synchronized with directory services such as Active Directory. Size is (PowerPivot Service service application, Central Administration Content limited access to one administrator. tempdb determined by number of users, groups, and the ratio of users to groups. Scaling guidance: DefaultPowerPivotServiceApplicationDB_) (SharePoint_AdminContent_) Small Holds all temporary tables and temporary stored procedures and Scaling guidance: Scale up the database that supports the service  Scale up the database that supports the service application instance. Stores data refresh schedules, and PowerPivot usage data that is copied Content database for the Central Administration site. fills any other temporary storage needs. The tempdb database is re- application instance.  Scale out by creating additional instances of the service application, from the central usage data collection database. Significant growth is Small Requirements: created every time the SQL Server instance is started. Scale-out by creating additional instances of the service application, however, the decision to create a separate service application is likely to unlikely. Medium  Must be co-located with Configuration database Co-location guidance: Locate on a separate spindle from all other however, the decision to create a separate service application is likely to be be based on business, rather than scale, requirements. When in use, PowerPivot stores additional data in content databases and in  Only one Central Administration Content database is supported per based on business, rather than scale, requirements. databases the Central Administration content database. Scaling guidance: Scale up farm. I/O patterns: Even Requirements: SQL Server 2012 Analysis Services, Business Intelligence or Scaling guidance: Scale up only, significant growth is unlikely. Usage Enterprise Edition. Social Tagging (Usage and Health Data Collection service application, Scaling guidance: Scale up. (User Profile service application and the Metadata Management service SharePoint_Logging) application, if tags are used for metadata, Installed on SharePoint Online or SQL Azure and also on-premise but not Microsoft SQL Server 2008 R2 (SP1) Reporting Services PerformancePoint Services User Profile Service Application_SocialDB_) provisioned by default. & Stores health monitoring and usage data temporarily, and also used for (PerformancePoint Services service application, Content Stores social tags and notes created by users along with their respective URLs. Size is determined by the number of tags and ratings created and reporting and diagnostics. The Usage database is the only SharePoint PerformancePoint Service _) Microsoft SQL Server 2012 Reporting Services (WSS_Content) Small used. Extra - large database that can be queried directly and have schema modified by either Stores temporary objects and persisted user comments and settings. Stores all site content, including site documents or files in document Small – extra-large Scaling guidance: Scale up the database that supports the service Microsoft or third-party applications. Scaling guidance: SQL Server Reporting Services is installed on a SQL Server report server. It stores items libraries, list data, Web part properties, audit logs, apps for  application instance. Scale-out by creating additional instances of the service The database size varies based on retention policy and actual traffic load. Scale up the database that supports the service application instance. such as reports, report-related items and resources, schedules, and subscriptions. It can SharePoint, and user names and rights. All of the data for a specific application, however, the decision to create a separate service application is Co-location guidance: Place on separate spindle  Scale out by creating additional instances of the service application, be configured as a stand-alone server (native mode), multiple servers in a farm, or it can site resides in one content database. Content databases can contain Small - large likely to be based on business, rather than scale, requirements. Scaling guidance: Scale up the database. however, the decision to create a separate service application is likely to be integrated with SharePoint Server (SharePoint mode). more than one site collection. Also stores data for Office Web I/O patterns: Read-heavy Requirements: Only one Usage and Health Data Collection service be based on business, rather than scale, requirements. Applications, if in use. The database size varies based on usage application instance is supported per farm. I/O patterns: Read-heavy SQL Server Reporting Services can be used with SharePoint Server 2013 Excel Services, pattern, for example the number and size of documents and the I/O patterns: Write-heavy PerformancePoint Services, Access Services, Project Server, and Visio Services. If you are number of users. running Access Services, then SQL Server 2012 is required. Important guidance: We strongly recommend limiting the size of State Service (State service application, InfoPath Forms Services, Visio Services, content databases to 200 GB to help ensure system performance. Subscription Settings Service Content database sizes up to 1 terabyte are supported only for large, SessionStateService_) (Microsoft SharePoint Foundation Subscription Settings service application, Stores temporary state information for InfoPath Forms Services, Exchange, single-site repositories and archives with non-collaborative I/O and SettingsServiceDB) Report Server Catalog SharePoint Search Service Application databases Small the chart Web Part, and Visio Services. Database size depends on the usage usage patterns, such as Records Centers. (ReportingService_) Stores features and settings information for hosted customers. This of features that store data in it. Scaling guidance: (Foundation and Server) database is not created by default but must be created by using Windows Medium - large Stores all report metadata including report definitions, report Scaling guidance: Scale-out by adding another State database using Small  Scale up a database that supports a site collection. history and snapshots, and scheduling information. When PowerShell or SQL Server. Windows PowerShell cmdlets.  Scale-out at the Web application level: add more content Search Administration ReportServer is in use, report documents are stored in Scaling guidance: I/O patterns: Read-heavy databases as needed to support additional site collections. (Search service application,  Scale up the database that supports the service application instance. SharePoint content databases. Search_Service_Application_DB_)  Scale-out by creating additional instances of the service application, Requirements: Must be located on the same database server Medium Hosts the Search application configuration and access control list (ACL) for however, the decision to create a separate service application is likely to Word Automation Services as the ReportServerTempDb database. the crawl component. be based on business, rather than scale requirements. (Word Automation Services service application, Supports service applications: Often used with Access Scaling guidance: Scale up the database that supports the service I/O patterns: Read-heavy WordAutomationServices_) Services, Excel Services, PerformancePoint Services, and Visio application instance. Small Stores information about pending and completed document conversions Services, but not required. Scale-out by creating additional instances of the service application, and updates. Scaling guidance: Scale up however, the decision to create a separate service application is likely to be Business Data Connectivity Legend Relative size: Small I/O patterns: Read-heavy based on business, rather than scale, requirements. (Business Data Connectivity service application, Scaling guidance: Scale up the database that supports the service Bdc_Service_DB_) application instance. (Significant growth is unlikely). Small Stores external content types and related objects. Database types Analytics Reporting I/O patterns: Read and write-heavy once per conversion item. (Search service application, Relative size: Small SharePoint 2013 Search service application Search_Service_Application_AnalyticsReportingStoreDB_) Scaling guidance: Scale up, (significant growth is unlikely). ReportServerTempDB system databases (ReportingService__TempDB) Stores the results for usage analysis reports and extracts information from I/O patterns: Read-heavy Managed Metadata Service (Foundation, Server) the Link database when needed. Stores all of the temporary snapshots while reports are User Profile service (Managed Metadata Service service application, Scaling guidance: Scale-out — add additional Analytics Reporting database running. The size varies frequently, depending on use of application Medium - large Managed Metadata Service Application_Metadata_) cached report snapshots. SharePoint 2013 using a split operation when the main database size becomes >200GB. Stores managed metadata and syndicated content types. common databases SQL Server 2008 R2 I/O patterns: Write-heavy during nightly analytics update. Medium Also stores the Taxonomy service metadata in a hierarchical structure for (Foundation, Server) SQL Server 2012 items that are used for tagging content and building site collections. Small – extra-large Crawl Relative size: Medium SharePoint Server 2013 SQL Server 2008 R2 Reporting (Search service application, Report Server Alerting (Standard, Enterprise) Services Scaling guidance: Scale up the database that supports the service SQL Server 2012 Reporting Search_Service_Application_CrawlStoreDB_) application instance. (ReportingService__Alerting) Services Stores the state of the crawled data and the crawl history. Scale-out by creating additional instances of the service application. This database is found in SQL Server 2012 only. Stores all Data Co-location guidance: In large-scale environments. I/O patterns: Read-heavy Alerts metadata and runtime information required to Medium Scaling guidance: Scale-out — add additional Crawl database per every 20 produce Data Alerts for Reporting Services operational million items crawled. reports. Data from reports is processed within the database Database size ranges Other notations I/O patterns: Read-heavy Machine Translation Services to match rules defined in Alert Definitions. The size varies (Database icons shown are not to Recommended SQL Server edition: Extra - large frequently, depending on use of Data Alerts scale) (SharePoint Translation Services service application, SQL Server 2008 R2 with Service Pack 1 (SP1) or SQL Server 2012, Enterprise SharePoint Translation Services_) Scaling guidance: Scale up; optimize file I/O; optimize edition, so that the Search service application can take advantage of data Small memory usage Very Small: Large: Stores information about pending and completed batch document 100 MB or less Up to 1 terabyte compression. translations with file extensions that are enabled. I/O patterns: Read-heavy, Write-heavy Relative size: Small Small: Link Up to 1 GB Scaling guidance: Scale up the database that supports the service (Search service application, application instance. (Significant growth is unlikely). Search_Service_Application_LinkStoreDB_) I/O patterns: Read-heavy Extra-large: Medium - large Stores the information that is extracted by the content processing Medium: 1 terabyte or more component and the click through information. Up to 100 GB Co-location guidance: On sites with heavy traffic we recommend the Links Apps for SharePoint database to utilize separate spindles from other databases. (Apps_) Scaling guidance: Scale-out — add additional Link database per 60 million Very small Stores information about apps for SharePoint and Access Apps. Support multiple documents crawled. Also add additional Link database per 100 million databases Scaling guidance: Scale up the database that supports the apps instance. expected queries per year. The Link database grows on disk by 1 GB per 1 (scales out) (Significant growth is unlikely). million documents fed. The click data grows linearly with query traffic, 1 GB I/O patterns: Read-heavy per million queries. I/O patterns: Write-heavy during content processing