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