Manage databases in SharePoint Server

APPLIES TO: yes2013 yes2016 yes2019 noSharePoint Online

The following articles and related resources provide information about database management with SharePoint Server.

Content Description
Add content databases in SharePoint Server
Adding a content database to an existing Web application is a common task. This article describes how to add a content database to an existing SharePoint Server implementation.
Attach or detach content databases in SharePoint Server
Certain operations, such as applying updates or creating copies of configuration settings, require that you detach and then attach databases. This article describes how to do these procedures.
Move site collections between databases in SharePoint Server
Under some circumstances, you might want to move one or more site collections to a different content database. For example, a site collection can outgrow the content database on which it is located, and you would have to move the site collection to a larger content database. Conversely, if site collections do not grow to their expected capacity, it might be convenient to combine several site collections onto one content database. This article describes how to move site collections between databases.
Move content databases in SharePoint Server
This article describes how to move content databases between servers that are running SQL Server, between instances of SQL Server, or from one SharePoint Server Web application to another. You can also move a content database to load balance a database server or Web application.
Move all databases in SharePoint Server
This article describes how to move all of the databases supported by SharePoint Server from one database server to another database server. If your SharePoint databases are hosted on different servers, this procedure applies to the database server that hosts the configuration database.
Move or rename service application databases in SharePoint Server
Learn how to move and rename service application databases by using SQL Server, and then how to point the service application to the moved or renamed database.
Run a farm that uses read-only databases in SharePoint Server
A read-only farm can be part of a disaster recovery environment. Alternatively, it can be part of a highly available maintenance, patching, or upgrade environment that provides user access while another version of the farm is being updated. This article describes how to run a SharePoint Server farm in which content databases are set to be read-only (a read-only farm).
Manage RBS in SharePoint Server
Learn about Remote BLOB Storage (RBS) and how to manage RBS in SharePoint Server.
Best practices for SQL Server in a SharePoint Server farm
Learn about best practices for SQL Server in a SharePoint Server farm.

See also

Concepts

Overview of backup and recovery in SharePoint Server

Plan for backup and recovery in SharePoint Server

Database types and descriptions in SharePoint Server