Use the cmdlet to resume a failed database upgrade or begin a build-to-build database upgrade against a SharePoint content database. The cmdlet initiates an upgrade of an existing content database that is attached to the current farm.

This cmdlet begins a new upgrade session, which can be used either to resume a failed version-to-version or build-to-build upgrade of a content database флористическая объемная композиция to begin a build-to-build upgrade of a content database.

If the database is hosted on a version of SQL Server that supports creation and use of snapshots of the database, this cmdlet can use a database snapshot for build-to-build upgrades.

During upgrade, users see a ready-only version of the database, which is the snapshot. After upgrade users see upgraded content.

The default behavior of this cmdlet causes an upgrade of the schema of the флористическая объемная композиция and initiates build-to-build upgrades for all site collections within the specified content database if required. To prevent build-to-build upgrades of site collections, use the NoB2BSiteUpgrade parameter.

This cmdlet does not trigger version-to-version upgrade of any site collections.

Examples

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

This example upgrades the флористическая объемная композиция WSS_Content content database schema 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------------------------------

This example upgrades the existing WSS_Content content database schema only. 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.

--------------------------EXAMPLE 3------------------------------

This example upgrades the existing WSS_Content content database schema only while using a snapshot of the database to retain read-only access to the content during the upgrade.

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.

Required Parameters

-Identity

Specifies the content database to upgrade.

The value must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh or an instance of a valid SPContentDatabase object.

Optional Parameters

Lets the upgrade process to proceed on a content database which is not currently attached to a SharePoint farm.

Type:

SwitchParameter

Position:

Named

Default value:

None

Accept pipeline input:

False

Accept wildcard characters:

False

Applies to:

SharePoint Server 2016

-AssignmentCollection

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.

When the Global parameter is used, флористическая объемная композиция objects are contained in the global store. If objects are not immediately used, or disposed of флористическая объемная композиция using the command, an out-of-memory scenario can occur.