Export (0) Print
Expand All

Manage databases in SharePoint 2013

Published: July 16, 2012

Summary: Learn how to manage the databases that are associated with SharePoint 2013.

Applies to:  SharePoint Foundation 2013 | SharePoint Server 2013 

The following articles on TechNet and related resources provide information about database management.

TechNet articles about database management

The following articles about database management are available to view online. Writers update articles on a continuing basis as new information becomes available and as users provide feedback.

Content Description

Building blocks

Add content databases in SharePoint 2013

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 2013 implementation.

Attach or detach content databases in SharePoint 2013

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 2013

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 2013

This article describes how to move content databases between servers that are running SQL Server, between instances of SQL Server, or from one SharePoint 2013 Web application to another. You can also move a content database to load balance a database server or Web application.

Rename service application databases in SharePoint 2013

This section describes how to rename service application databases by using SQL Server, and then how to point the service application to the renamed database. This can be a complex process because different types of service applications require different methods of pointing to the new database name. Each article describes how to rename a specific service application database and then how to point to the renamed database.

Move service application databases (SharePoint 2013)

This section describes how to move service application databases by using SQL Server, and then how to point the service application to the moved database. This can be a complex process because different types of service applications require different methods of pointing to the new database name. Each article describes how to move a specific service application database and then how to point to the moved database.

Move all databases in SharePoint 2013

This article describes how to move all of the databases associated with SharePoint 2013 from one database server to another database server. If your databases are hosted on different servers, this procedure applies to the database server that hosts the configuration database.

Run a farm that uses read-only databases in SharePoint 2013

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 2013 farm in which content databases are set to be read-only (a read-only farm).

Manage RBS in SharePoint 2013

Learn about Remote BLOB Storage (RBS) and how to manage RBS in SharePoint 2013.

Best practices for SQL Server in a SharePoint Server farm

Learn how to implement best practices for SQL Server in a SharePoint Server 2013 farm.

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