Mount-SPContentDatabase

 

Applies to: SharePoint Server 2016

Topic Last Modified: 2015-11-23

Attaches an existing content database to the farm.

Mount-SPContentDatabase -Name <String> -WebApplication <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-AssignNewDatabaseId <SwitchParameter>] [-ChangeSyncKnowledge <SwitchParameter>] [-ClearChangeLog <SwitchParameter>] [-Confirm [<SwitchParameter>]] [-DatabaseAccessCredentials <PSCredential>] [-DatabaseCredentials <PSCredential>] [-DatabaseFailoverServer <String>] [-DatabaseServer <String>] [-MaxSiteCount <Int32>] [-SkipIntegrityChecks <SwitchParameter>] [-SkipSiteUpgrade <SwitchParameter>] [-UseLatestSchema <SwitchParameter>] [-WarningSiteCount <Int32>] [-WhatIf [<SwitchParameter>]]

-----------------EXAMPLE 1---------------------

Mount-SPContentDatabase "MyDatabase" -DatabaseServer "MyServer" -WebApplication http://sitename

This example mounts an existing database to the sitename web application. If upgrades are required, it triggers database schema upgrade and then performs only build-to-build upgrade actions on existing site collections if required. This operation does not changed the CompatibilityLevel for existing site collections in this database.

-----------------EXAMPLE 2---------------------

Mount-SPContentDatabase "MyDatabase" -DatabaseServer "MyServer" -WebApplication http://sitename -NoB2BSiteUpgrade

This example mounts an existing database to the sitename web application but it prevents any site upgrades from occurring. If upgrades are required, it triggers database schema upgrades only and no build-to-build upgrade actions are performed on any site collections. This operation does not change the CompatibilityLevel for existing site collections in this database.

The Mount-SPContentDatabase cmdlet attaches an existing content database to the farm. If the database being mounted requires an upgrade, this cmdlet will cause the database to be upgraded.

The default behavior of this cmdlet causes an upgrade of the schema of the database and initiates upgraded builds for all site collections within the specified content database if required. To prevent initiation of upgraded builds of site collections, use the NoB2BSiteUpgrade parameter. This cmdlet does not trigger version-to-version upgrade of any site collections.

For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at Windows PowerShell for SharePoint Server 2016 reference.

 

Parameter Required Type Description

Name

Required

System.String

Specifies the existing content database to attach to the farm.

The type must be a valid name of a SharePoint content database; for example, SPContentDB1.

WebApplication

Required

Microsoft.SharePoint.PowerShell.SPWebApplicationPipeBind

Attaches the content database to the specified SharePoint web application.

The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of SharePoint web application (for example, MyOfficeApp1); or an instance of a valid SPWebApplication object.

AssignmentCollection

Optional

Microsoft.SharePoint.PowerShell.SPAssignmentCollection

Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used.

NoteNote:
When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur.

AssignNewDatabaseId

Optional

System.Management.Automation.SwitchParameter

Creates a new database ID automatically when the content database is attached.

ChangeSyncKnowledge

Optional

System.Management.Automation.SwitchParameter

Database attach will cause all Groove sync client to re-synchronize their content.

ClearChangeLog

Optional

System.Management.Automation.SwitchParameter

Clears any pending changes from the change log in the content database.

Confirm

Optional

System.Management.Automation.SwitchParameter

Prompts you for confirmation before executing the command. For more information, type the following command: get-help about_commonparameters

DatabaseAccessCredentials

Optional

System.Management.Automation.PSCredential

Specifies the credential that belong to SPDataAccess role.

DatabaseCredentials

Optional

System.Management.Automation.PSCredential

Specifies the PSCredential object that contains the user name and password to be used for database SQL Authentication.

The type must be a valid PSCredential object.

DatabaseFailoverServer

Optional

System.String

Specifies the name of the database server to be mirrored.

DatabaseServer

Optional

System.String

Specifies the name of the host server for the content database specified in the Name parameter.

The type must be a valid SQL Server host name; for example, SQLServerHost1.

MaxSiteCount

Optional

System.Int32

Specifies the maximum number of web sites that can use the content database.

The type must be a positive integer.

SkipIntegrityChecks

Optional

System.Management.Automation.SwitchParameter

Specifies the upgrade process not to run the internal integrity checks such as missing templates, and orphan detection as part of the upgrade process.

SkipSiteUpgrade

Optional

System.Management.Automation.SwitchParameter

Specifies to not upgrade all site objects when performing upgrade.

UseLatestSchema

Optional

System.Management.Automation.SwitchParameter

Specifies to use the latest schema. In an on-premises environment, this parameter has no effect.

There are two values $True and $False.

The default value is False.

WarningSiteCount

Optional

System.Int32

Specifies the number of sites that can be created before a warning event is generated and the owner of the site collection is notified.

The type must be a positive integer.

WhatIf

Optional

System.Management.Automation.SwitchParameter

Displays a message that describes the effect of the command instead of executing the command. For more information, type the following command: get-help about_commonparameters

 
Show: