Export (0) Print
Expand All

Database types and descriptions (SharePoint 2013)

Updated: May 14, 2013

Summary: Learn about sizing and location information about the databases that support SharePoint 2013.

Applies to:  SharePoint Foundation 2013 | SharePoint Server 2013 

This article describes the databases that are installed for SharePoint 2013. Each database description includes information about sizing and placement. For more information see Storage and SQL Server capacity planning and configuration (SharePoint Server 2013).

Databases for SharePoint 2013 can be hosted in SQL Server 2008 R2 with Service Pack 1 (SP1) or SQL Server 2012. For more information see Hardware and software requirements for SharePoint 2013.

All database names that are listed in this article are automatically created when you run the SharePoint Products Configuration Wizard. You do not have to use these naming conventions. You can either specify your own database names when you create them or change the names after they are created. For more information, see Rename service application databases in SharePoint 2013

The database sizes listed in this article are based on the following ranges.

Descriptor Size range

Very Small

Up to 100 megabyte (MB)

Small

1 gigabyte (GB) or less

Medium

Up to 100 GB

Large

Up to 1 terabyte

Extra-large

More than 1 terabyte

In this article:

For a graphical overview of the databases that support SharePoint 2013, see Database model.

SharePoint 2013 databases

The following databases are part of all SharePoint 2013 deployments. These databases are installed when any SharePoint 2013 edition is deployed. The Configuration, Central Administration Content, and Content databases are the 3 databases that are automatically installed when you deploy SharePoint 2013.

Configuration

The configuration database contains data about the following:

  • SharePoint databases

  • Internet Information Services (IIS) web sites

  • Web applications

  • Trusted solutions

  • Web Part packages

  • Site templates

  • Web applications

The configuration database also contains specific data for SharePoint 2013 farm settings, such as default quota settings and blocked file types.

Configuration database

Category Description

Default database name when it is installed with the SharePoint Products Configuration Wizard

SharePoint_Config

Location requirements

Must be co-located with the Central Administration database

General size information and growth factors

Small

Transaction log files that are stored in the configuration database are likely to become large. For more information, see Additional notes.

Read/write characteristics

Read-intensive

Recommended scaling method

Must scale-up because only one configuration database is supported per farm. (Significant growth is unlikely.)

Associated health rules

None

Supported backup tools

SharePoint 2013 backup and restore, SQL Server, and System Center 2012 - Data Protection Manager (DPM). Backing up and restoring the configuration databases is special because of the transaction log. For more information, see Additional notes.

Default recovery model

Full. We recommend that you switch the configuration database to the simple recovery model to restrict growth of the log file.

Additional notes

Transaction log files. We recommend that you back up the transaction log for the configuration database regularly to force truncation. If you are mirroring your system, then change the database to run in Full recovery mode. For more information, see Transaction Log Truncation.

Backup and Restore. The configuration database is backed up when you perform a SharePoint farm configuration and content backup. Note that some configuration settings from the database are exported and stored as XML file. When a farm is restored, the configuration database is not restored. Instead, the saved configuration settings are imported. The configuration database can be successfully backed up and restored by using SQL Server or other tools if the SharePoint farm is first taken offline.

note Note:

Many configuration settings are not saved during a farm configuration-only backup or restore. These configuration settings may include particular Web application settings, service application settings, and settings that are specific to the local server. These settings are saved during a farm content and configuration backup. But some of them, such as service application proxy settings, cannot be restored during a farm recovery. For information about what is saved during a configuration backup, see Back up farm configurations in SharePoint 2013. For information about how to document and copy configuration settings that are not backed up, see Copy configuration settings between farms in SharePoint 2013.

Central Administration content

The Central Administration content database is considered to be a configuration database. It stores all configuration data for the Central Administration site collection. If SQL Server 2012 Power Pivot for SharePoint 2013 is installed, the Central Administration content database also stores the Excel worksheets and Power Pivot data files used in the Power Pivot Management Dashboard. Note that Power Pivot for SharePoint 2013 can only be installed on SharePoint Server 2013.

Central Administration content database

Category Description

Default database name prefix when it is installed by using the SharePoint Products Configuration Wizard

SharePoint_AdminContent_<GUID>

Location requirements

Must be located on the same database engine instance with the configuration database.

General size information, and growth factors

Small

If you use Power Pivot for SharePoint 2013 and use the default settings that keep usage data collection and data refresh history for 365 days, the Central Administration content database will grow over the span of one year. For more information about Power Pivot for SharePoint 2013, see Plan a PowerPivot Deployment in a SharePoint Farm.

Read/write characteristics

Varies

Recommended scaling method

Must scale-up. The database must grow larger because only one Central Administration content database is supported per farm. (Significant growth is unlikely.)

Associated Health rules

None

Supported backup tools

SharePoint 2013 backup and restore, SQL Server, and System Center 2012 - Data Protection Manager (DPM). Backing up and restoring the Central Administration content databases is special. For more information, see Additional notes.

Default recovery model

Full

Additional notes

Backup and restore. The Central Administration content database is backed up when you perform a SharePoint farm configuration and content backup. When a farm is restored, the Central Administration content database is not restored. The Central Administration content database can be successfully backed up and restored by using SQL Server or other tools if the SharePoint farm is first taken offline.

Content databases

Content databases store all content for a site collection. This includes site documents or files in document libraries, list data, Web Part properties, audit logs, and sandboxed solutions, in addition to user names and rights.

All of the files that are stored for a specific site collection are located in one content database on only one server. A content database can be associated with more than one site collection.

Content databases also store user data for Power Pivot for SharePoint, if you installed it in your SharePoint Server 2013 environment. Note that Power Pivot for SharePoint can only be installed on SharePoint Server 2013

Content database

Category Description

Default database name when installed by using the SharePoint Products Configuration Wizard

WSS_Content

Location requirements

None

General size information and growth factors

We recommend limiting the size of content databases to 200 GB to help ensure system performance. For more information, see Additional notes.

Content database size varies significantly by usage. For more information, see Additional notes.

Read/write characteristics

Varies by usage. For example, collaboration environments are write-intensive and document management environments are read-intensive.

Recommended scaling method

Content databases that support a site collection must scale-up. The database must be able to grow larger as needed. You can create additional site collections that are associated with a Web application and associate the new site collection with a different content database. If a content database is associated with multiple site collections, you can move a site collection to another database. For information about how to size content databases, see Storage and SQL Server capacity planning and configuration (SharePoint Server 2013).

Associated Health rules

None

Supported backup tools

SharePoint 2013 backup and restore, SQL Server, and System Center 2012 - Data Protection Manager (DPM).

Default recovery model

Full

Additional notes

Recommended content database size limitations

Content database sizes up to 1 terabyte are supported only for large, single-site repositories and archives in which data remains reasonably static, such as reference document management systems and Records Center sites. Larger database sizes are supported for these scenarios because their I/O patterns and typical data structure formats have been designed for, and tested at, larger scales. For more information about large-scale document repositories, see "Estimate Performance and Capacity Requirements for Large Scale Document Repositories", available from Storage and SQL Server capacity planning and configuration (SharePoint Server 2013).

Content database size estimation

Content database size varies significantly with the usage of the site. Growth factors include the number of documents, number of users, use of versioning, use of Recycle Bins, size of quotas, whether the audit trail is configured, and how many items are chosen for auditing.

If Power Pivot for SharePoint is being used, the Excel files stored in SharePoint Server grow larger, which increases the size of the content database. For more information, see Plan a PowerPivot Deployment in a SharePoint Farm.

For detailed recommendations about how to calculate the size of a content database, see Storage and SQL Server capacity planning and configuration (SharePoint Server 2013).

SharePoint 2013 service application databases

The following service application databases are available in both SharePoint Foundation 2013 and SharePoint Server 2013 deployments.

App Management database

The App Management database is used by the App Management Service application. It stores the app licenses and permissions that are downloaded from the SharePoint Store or App Catalog.

App Management database

Category Description

Default database name when installed by using the SharePoint Products Configuration Wizard

AppManagement

Location requirements

None

General size information and growth factors

Small. Scale-up when the service application database reaches 10 GB. Scale out only on SharePoint Online.

Read/write characteristics

Write-heavy during apps installation and license renewal.

Recommended scaling method

App License Management databases can scale out only on SharePoint Online.

Associated Health rules

None

Supported backup tools

SharePoint 2013 backup and restore, Windows PowerShell, and SQL Server.

Default recovery model

Full

Business Data Connectivity service application database

The Business Data Connectivity service application database stores external content types and related objects.

Business Data Connectivity database

Category Description

Default database name when installed by using the SharePoint Products Configuration Wizard

Bdc_Service_DB_<GUID>

Location requirements

None

General size information and growth factors

Small. Size is determined by the number of connections.

Read/write characteristics

Read-heavy

Recommended scaling method

Must scale-up. The database must grow larger, because only one Business Data Connectivity database is supported per farm. (Significant growth is unlikely.)

Associated Health rules

None

Supported backup tools

SharePoint 2013 backup and restore, Windows PowerShell, and SQL Server.

Default recovery model

Full

Search service application databases

The Search service application has four databases that support SharePoint 2013. The four Search service application databases are shown in the following list. The tables that follow the list display the relevant database information.

  • Search Administration: The Search Administration database hosts the Search service application configuration and access control list (ACL) for the crawl component.

  • Analytics Reporting: The Analytics Reporting database stores the results for usage analysis reports and extracts information from the Link database when needed.

  • Crawl: The Crawl database stores the state of the crawled data and the crawl history.

  • Link: The Link database stores the information that is extracted by the content processing component and the click through information.

Search Administration database

Category Description

Default database name when installed by using the SharePoint Products Configuration Wizard

Search_Service_Application_DB_<GUID>

Location requirements

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.

General size information and growth factors

Medium. 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.

Read/write characteristics

Equal read/write ratio

Recommended scaling method

Scale-up the database that supports the service application instance. Scale out by creating additional instances of the service application, however, the decision to create a separate service application is likely to be based on business, rather than scale, requirements.

Associated Health rules

None

Supported backup tools

SharePoint 2013 backup and restore, Windows PowerShell, and SQL Server.

Default recovery model

Simple

Analytics Reporting database

Category Description

Default database name when installed by using the SharePoint Products Configuration Wizard

Search_Service_Application_AnalyticsReportingStoreDB_<GUID>

Location requirements

None

General size information and growth factors

Medium to large.

Read/write characteristics

Write heavy during nightly analytics update.

Recommended scaling method

Scale out by creating additional Analytics Reporting database using a split operation when the main database becomes >200 GB.

Associated Health rules

None

Supported backup tools

SharePoint 2013 backup and restore, Windows PowerShell, and SQL Server.

Default recovery model

Simple

Crawl database

Category Description

Default database name when installed by using the SharePoint Products Configuration Wizard

Search_Service_Application_CrawlStoreDB_<GUID>

General size information and growth factors

Medium.

Read/write characteristics

Read heavy.

Recommended scaling method

Scale out by creating additional Crawl database per every 20 million items crawled.

Associated Health rules

None

Supported backup tools

SharePoint 2013 backup and restore, Windows PowerShell, and SQL Server.

Default recovery model

Simple

Link database

Category Description

Default database name when installed by using the SharePoint Products Configuration Wizard

Search_Service_Application_LinkStoreDB_<GUID>

Location requirements

We recommend that if you have sites that have heavy traffic, the Link database should use separate spindles from other databases.

General size information and growth factors

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.

Read/write characteristics

Write heavy during content processing.

Recommended scaling method

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.

Associated Health rules

None

Supported backup tools

SharePoint 2013 backup and restore, Windows PowerShell, and SQL Server.

Default recovery model

Simple

Secure Store Service database

The Secure Store Service application database stores and maps credentials, such as account names and passwords.

Secure Store database

Category Description

Default database name when installed by using the SharePoint Products Configuration Wizard

Secure_Store_Service_DB_<GUID>

Location requirements

For secure credential storage, we recommend that the Secure Store database be hosted on a separate database instance or database server that has access limited to one administrator. By default, if the database is hosted on the default SharePoint database server and instance, all database administrators will have access to the Secure Store database.

General size information and growth factors

Small. Size and growth are determined by the number of target applications, number of credential fields per target application, and the number of users stored in each target application. If auditing is turned on, the number of read and write operations performed against a given target application also affects size.

Read/write characteristics

Equal read/write ratio

Recommended scaling method

Scale-up the database that supports the service application instance. You can scale out by creating additional instances of the service application, however, the decision to create a separate service application is likely to be based on business, rather than scale, requirements.

Associated Health rules

None

Supported backup tools

SharePoint 2013 backup and restore, Windows PowerShell, and SQL Server.

Default recovery model

Full

Usage and Health Data Collection database

The Usage and Health Data Collection database is used by the Usage and Health Data Collection service application. It stores health monitoring and usage data temporarily, and can be used for reporting and diagnostics. The Usage and Health Data Collection database is the only SharePoint database that supports schema modifications.

note Note:

For more information on supported Read operations, see "Read Operations Addendum" in KB 841057: Support for changes to the databases that are used by Office server products and by Windows SharePoint Services.

Usage database

Category Description

Default database name when installed by using the SharePoint Products Configuration Wizard

SharePoint_Logging

Location requirements

The Usage and Health Data Collection database is very active, and should be put on a separate disk or spindle, if it is possible.

General size information and growth factors

Extra large. Database size depends on the retention factor, number of items enabled for logging and external monitoring, how many Web applications are running in the environment, how many users are currently working, and which features are enabled.

Read/write characteristics

Write-heavy

Recommended scaling method

Must scale-up. That is, the database must grow larger, because only one Usage and Health Data Collection service application instance is supported per farm.

Associated Health rules

None

Supported backup tools

Windows PowerShell, and SQL Server.

Default recovery model

Simple

Subscription Settings Service database

The Microsoft SharePoint Foundation Subscription Settings service application database stores features and settings for hosted customers. The Subscription Settings service application and database are not created by the SharePoint Products Configuration Wizard — they must be created by using Windows PowerShell cmdlets or SQL Server. For more information, see New-SPSubscriptionSettingsServiceApplication.

Subscription Settings database

Category Description

Default database name when installed by using the Windows PowerShellNew-SPSubscriptionSettingsServiceApplication cmdlet

SettingsServiceDB

Location requirements

None

General size information and growth factors

Small. Size is determined by the number of tenants, farms, and features supported.

Read/write characteristics

The subscription database is read-heavy.

Recommended scaling method

Scale-up the database that supports the service application instance. You can scale out by creating additional instances of the service application, however, the decision to create a separate service application is likely to be based on business, rather than scale, requirements.

Associated Health rules

None

Supported backup tools

SharePoint 2013 backup and restore, Windows PowerShell, and SQL Server.

Default recovery model

Full

SharePoint Server 2013 databases

The following databases are available in a SharePoint Server 2013 deployment.

SharePoint User Profile service application databases

The User Profile service has three databases that support SharePoint Server 2013. The three User Profile service databases are shown in the following list. The tables that follow the list display the relevant database information.

  • Profile: The Profile database stores and manages users and associated information. It also stores information about a user's social network in addition to memberships in distribution lists and sites.

  • Synchronization: The Synchronization database stores configuration and staging data for use when profile data is being synchronized with directory services such as Active Directory.

  • Social Tagging: The Social Tagging database stores social tags and notes created by users, alongside their respective URLs.

Profile database

Category Description

Default database name when installed by using the SharePoint Products Configuration Wizard

User Profile Service Application_ProfileDB_<GUID>

Location requirements

None

General size information and growth factors

Medium to large. Growth factors include additional users and the use of news feeds. News feeds grow with user activities. The default is to maintain the last two weeks of activity, after which a time job deletes the news feed items older than two weeks.

Read/write characteristics

Read-heavy

Recommended scaling method

Scale-up the database that supports the service application instance. You can scale out by creating additional instances of the service application, however, the decision to create a separate service application is likely to be based on business, rather than scale, requirements.

Associated Health rules

None

Supported backup tools

SharePoint 2013 backup and restore, Windows PowerShell, and SQL Server.

Default recovery model

Simple

Synchronization database

Category Description

Default database name when installed by using the SharePoint Products Configuration Wizard

User Profile Service Application_SyncDB_<GUID>

Location requirements

None

General size information and growth factors

Medium to large. Growth factors include the number of users, groups, and the ratio of users to groups.

Read/write characteristics

Equal read/write ratio.

Recommended scaling method

Scale-up the database that supports the service application instance. You can scale out by creating additional instances of the service application, however, the decision to create a separate service application is likely to be based on business, rather than scale, requirements.

Associated Health rules

None

Supported backup tools

SharePoint 2013 backup and restore, Windows PowerShell, and SQL Server.

Default recovery model

Simple

Social Tagging database

Category Description

Default database name when installed by using the SharePoint Products Configuration Wizard

User Profile Service Application_SocialDB_<GUID>

Location requirements

None

General size information and growth factors

Small to extra-large. Growth factors include the number of tags, ratings, and notes that have been created and used.

Read/write characteristics

Read-heavy

Recommended scaling method

Scale-up the database that supports the service application instance. You can scale out by creating additional instances of the service application, however, the decision to create a separate service application is likely to be based on business, rather than scale, requirements.

Associated Health rules

None

Supported backup tools

SharePoint 2013 backup and restore, Windows PowerShell, and SQL Server.

Default recovery model

Simple

Word Automation Services service application database

The Word Automation Services database stores information about pending and completed document conversions and updates. The Word Automation Services Timer Job processes and distributes this information as queued conversion job items to application servers.

Word Automation Services database

Category Description

Default database name when installed by using the SharePoint Products Configuration Wizard

WordAutomationServices_<GUID>

Location requirements

None

General size information and growth factors

Small

Read/write characteristics

Read-heavy, once per conversion item.

Recommended scaling method

Scale-up the database that supports the service application instance. You can scale out by creating additional instances of the service application, however, the decision to create a separate service application is likely to be based on business, rather than scale, requirements.

Associated Health rules

None

Supported backup tools

SharePoint 2013 backup and restore, Windows PowerShell, and SQL Server.

Default recovery model

Full

Managed Metadata Service service application database

The Managed Metadata service application database stores managed metadata and syndicated content types.

Important Important:

The Taxonomy service works in conjunction with the Managed Metadata Service that provides the Term Store Management Tool in the SharePoint Central Administration website. This means that the Managed Metadata service application database stores the metadata for the Taxonomy service. The Taxonomy service metadata is stored in a hierarchical structure for items that are used for tagging content and building site collections.

Managed Metadata database

Category Description

Default database name when installed by using the SharePoint Products Configuration Wizard

Managed Metadata Service Application_Metadata_<GUID>

Location requirements

None

General size information and growth factors

Medium. Growth factors include the amount of managed metadata.

Read/write characteristics

Read-heavy

Recommended scaling method

Scale-up the database that supports the service application instance. Scale out by creating additional instances of the service application

Associated Health rules

None

Supported backup tools

SharePoint 2013 backup and restore, Windows PowerShell, and SQL Server.

Default recovery model

Full

SharePoint Translation Services service application database

The Machine Translation Services stores information about pending and completed batch document translations with file extensions that are enabled.

Machine Translation Services database

Category Description

Default database name when installed by using the SharePoint Products Configuration Wizard

SharePoint Translation Services_<GUID>

Location requirements

None

General size information and growth factors

Small

Read/write characteristics

Read-heavy

Recommended scaling method

Scale-up the database that supports the service application instance. You can scale out by creating additional instances of the service application, however, the decision to create a separate service application is likely to be based on business, rather than scale, requirements.

Associated Health rules

None

Supported backup tools

SharePoint 2013 backup and restore, Windows PowerShell, and SQL Server.

Default recovery model

Full

Project Server service application database

Project Server creates a separate database for each instance of Project Web App. Each Project Web App database contains the following data:

  • All Project and Portfolio Management (PPM) data

  • Time tracking and Timesheet data

  • Aggregated SharePoint project site data

Project Server database

Category Description

Default database name when installed by using the SharePoint Products Configuration Wizard

ProjectWebApp

Location requirements

None

General size information and growth factors

Small to medium.

Read/write characteristics

Read-heavy

Recommended scaling method

Scale-up the SQL Server that hosts the Project Web App database. (Significant growth is unlikely.)

Associated Health rules

None

Supported backup tools

SharePoint 2013 backup and restore, Windows PowerShell, and SQL Server.

Default recovery model

Full

SQL Server Power Pivot Service service application database

The Power Pivot Service database stores data refresh schedules, and Power Pivot usage data that is copied from the central usage data collection database.

Important Important:

SQL Server 2012 Power Pivot for SharePoint 2013 requires SQL Server 2012 Analysis Services (SSAS), Business Intelligence or Enterprise edition.

note Note:

When being used, Power Pivot stores additional data in content databases and in the Central Administration Content database (WSS_Content).

Power Pivot database

Category Description

Default database name when installed by using the SharePoint Products Configuration Wizard

DefaultPowerPivotServiceApplicationDB_<GUID>

Location requirements

None

General size information and growth factors

Small.

Read/write characteristics

Read-heavy

Recommended scaling method

Scale-up. (Significant growth is unlikely.)

Associated Health rules

None

Supported backup tools

SharePoint 2013 backup and restore, Windows PowerShell, and SQL Server.

Default recovery model

Full

PerformancePoint Services service application database

The PerformancePoint Services database stores temporary objects and persisted user comments and settings.

PerformancePoint Services database

Category Description

Default database name when installed by using the SharePoint Products Configuration Wizard

PerformancePoint Service _<GUID>

Location requirements

None

General size information and growth factors

Small.

Read/write characteristics

Read-heavy

Recommended scaling method

Scale-up the database that supports the service application instance. Scale out by creating additional instances of the service application, however, the decision to create a separate service application is likely to be based on business, rather than scale requirements.

Associated Health rules

None

Supported backup tools

SharePoint 2013 backup and restore, Windows PowerShell, and SQL Server.

Default recovery model

Full

State Service service application database

The State Service database stores temporary state information for InfoPath Forms Services, Exchange Server, the chart Web Part, and Visio Services.

State Service database

Category Description

Default database name when installed by using the SharePoint Products Configuration Wizard

SessionStateService_<GUID>

Location requirements

None

General size information and growth factors

Medium to large, depending on usage of features that store data in the State Service database.

Read/write characteristics

Read-heavy

Recommended scaling method

Scale out by creating another State Service database with Windows PowerShell cmdlets.

Associated Health rules

None

Supported backup tools

SharePoint 2013 backup and restore, Windows PowerShell, and SQL Server.

Default recovery model

Full

SQL Server system databases

SharePoint Server 2013 is built on SQL Server and uses the SQL Server system databases. SQL Server does not let users directly update information in system objects such as system tables, system stored procedures, and catalog views. Instead, SQL Server provides a complete set of administrative tools that let users fully administer their system and manage all users and objects in a database. For more information about the SQL Server system databases, see System Databases.

master database

The master database records all the system-level information for a SQL Server instance. This includes logins, configurations, and other databases.

master

Category Description

Default database name

master

Location requirements

The master database must be located on the same SQL Server instance that SharePoint uses.

General size information and growth factors

Small

Read/write characteristics

Varies

Recommended scaling method

Scale-up. (Significant growth is unlikely.)

Associated Health rules

None

Supported backup tools

SQL Server backup and restore.

Default recovery model

Simple

model database

The model database is used as the template for all databases created on the SQL Server instance. Any modifications made to the model database are also applied to all databases created afterward.

model

Category Description

Default database name

model

Location requirements

The model database must be located on the same SQL Server instance that SharePoint uses.

General size information and growth factors

Small

Read/write characteristics

Varies

Recommended scaling method

Scale-up. (Significant growth is unlikely.)

Associated Health rules

None

Supported backup tools

SQL Server backup and restore.

Default recovery model

Full

msdb database

The msdb database is used by SQL Server Agent for scheduling alerts and jobs.

msdb

Category Description

Default database name

msdb

Location requirements

The msdb database must be located on the same SQL Server instance that SharePoint uses.

General size information and growth factors

Small

Read/write characteristics

Varies

Recommended scaling method

Scale-up. (Significant growth is unlikely.)

Associated Health rules

None

Supported backup tools

SQL Server backup and restore.

Default recovery model

Simple

tempdb database

The tempdb database holds temporary objects or intermediate result sets. For example, it holds all temporary tables, temporary stored procedures, and any other temporary storage needs. The tempdb is recreated every time SQL Server starts.

tempdb

Category Description

Default database name

tempdb

Location requirements

Locate on a fast disk, on a separate spindle from other databases. Create as many files as needed to maximize disk bandwidth. Using multiple files reduces tempdb storage contention and yields significantly better scalability. However, do not create too many files because this can decrease performance and increase management overhead. As a general guideline, create one data file for each CPU on the server and adjust the number of files up or down as necessary. Note that a dual-core is two CPUs.

General size information and growth factors

Medium, depending on activities such as how many users are using the system, in addition to the specific processes that are running. For example, online rebuilds of large indexes, or large sorts cause the database to grow quickly.

Read/write characteristics

Varies

Recommended scaling method

Scale-up. (Significant growth is unlikely.)

Associated Health rules

None

Supported backup tools

SQL Server backup and restore.

Default recovery model

Simple

SQL Server Reporting Services databases

The following SQL Server Reporting Services (SSRS) can be used as part of a SharePoint 2013 deployment.

note Note:

If you are running Access Services in SharePoint Server 2013, then SQL Server 2012 is required. The requirements for Reporting Services depend on the mode in which you are running, as follows:

  • Local mode requires only SharePoint Server 2013 and the SQL Server Reporting Services Add-in.

  • Connected mode requires SharePoint Server 2013, the SSRS Add-in, and SQL Server 2012, available in Standard or Enterprise Edition.

Report Server Catalog database

The SQL Server Reporting Services Report Server Catalog database stores all report metadata including report definitions, report history and snapshots, and scheduling information. When Report Server Catalog is used, report documents are stored in SharePoint content databases.

Report Server Catalog

Category Description

Default database name

ReportingService_<GUID>

Location requirements

Must be located on the same database server as the ReportServerTempDb database.

General size information and growth factors

Small

Read/write characteristics

Read heavy

Recommended scaling method

Scale-up the database.

Associated Health rules

None

Supported backup tools

SQL Server backup and restore.

Default recovery model

Full

ReportServerTempDB database

The SQL Server Reporting Services ReportServerTempDB database stores all the temporary snapshots while reports are running.

ReportServerTempDB

Category Description

Default database name

ReportingService_<GUID>_TempDB

Location requirements

Must be located on the same database server as the Report Server Catalog database.

General size information and growth factors

This database size varies and goes from small to extra-large frequently. The size depends on use of cached report snapshots.

Read/write characteristics

Read heavy

Recommended scaling method

Scale-up the database.

Associated Health rules

None

Supported backup tools

SQL Server backup and restore, but we do not recommend that you back up this database.

Default recovery model

Full

Report Server Alerting database

The Report Server Alerting database stores all Data Alerts metadata and runtime information that is required to produce Data Alerts for Reporting Services operational reports. Data from reports is processed in the database to match rules that are defined in Alert Definitions.

Report Server Alerting

Category Description

Default database name

ReportingService_<GUID>_Alerting

Location requirements

Must be located on the same database server as the Report Server Catalog database.

General size information and growth factors

This database size varies and goes from small to extra-large frequently. The size depends on use of Data Alerts.

Read/write characteristics

Equal read heavy and write heavy.

Recommended scaling method

Scale-up to optimize the file I/O and memory usage.

Associated Health rules

None

Supported backup tools

SQL Server backup and restore.

Default recovery model

Full

Change History

Date Description

May 14, 2013

Updated the "Managed Metadata Service service application database" section to show that the Managed Metadata Service application database stores the Taxonomy service application metadata.

October 16, 2012

Initial publication

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft