Database management (SharePoint Foundation 2010)
Applies to: SharePoint Foundation 2010
This section describes techniques for managing the databases that are associated with Microsoft SharePoint Foundation 2010.
In this section:
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 Foundation 2010 implementation.
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.
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.
This article describes how to move content databases between servers that are running Microsoft SQL Server, between instances of SQL Server, or from one Microsoft SharePoint Foundation 2010 Web application to another. You can also move a content database to load balance a database server or Web application.
This article describes how to rename or move service application databases by using SQL Server, and then how to point the service application to the renamed or moved database. This can be a complex process because different types of service applications require different methods of pointing to the new database name or location. This article directs you to the supported method of pointing to a renamed or moved database for each service application.
This article describes how to move all of the databases associated with SharePoint Foundation 2010 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.
This article describes how to move RBS-enabled collaboration sites from content databases that are larger than 200GB to smaller content databases to achieve greater performance and to meet support requirements.
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 Foundation 2010 farm in which content databases are set to be read-only (a read-only farm).
This paper provides guidance and procedures for administering content databases in three size ranges: up to 200 gigabytes (GB), 200 GB-4 terabytes (TB), and larger than 4 TB.
This white paper provides information and guidelines for maintaining the databases that host data and configurations for SharePoint 2010 Products.
Remote BLOB Storage (RBS) is an add-on feature pack for Microsoft SQL Server 2008. RBS is designed to move the storage of binary large objects (BLOBs) from database servers to commodity storage solutions. If the content databases in SharePoint Foundation 2010 are 4 gigabytes (GB) or larger, consider using RBS as part of your data storage solution. This article introduces RBS.