Come and Check our BETA Alpha version of Powershellcenter.net
Send me your comment to Powershell@powershellcenter.com

Synopsis

Starts the upgrade process on a site collection.

Syntax

Upgrade-SPSite [-Identity] <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Email <SwitchParameter>] [-QueueOnly <SwitchParameter>] [-Unthrottled <SwitchParameter>] [-VersionUpgrade <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

Detailed Description

The Upgrade-SPSite cmdlet starts the upgrade process on a site collection. The Upgrade-SPSite cmdlet activates the upgrade process for the specified SPSite object. You can also use this cmdlet to resume failed upgrades. When you use this cmdlet to initiate upgrade on an SPSite object, the object can be either a build-to-build or version-to-version upgrade. By default, the Upgrade-SPSite cmdlet operates as a build-to-build upgrade. This prevents unexpected version upgrades of site collections if you use this cmdlet after a patching operation. When in version-to-version upgrade mode, site collection health checks are run in repair mode to ensure that the site collection is healthy enough to upgrade successfully. If successful, the remainder of the upgrade occurs. For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation at http://go.microsoft.com/fwlink/p/?LinkId=251831 (http://go.microsoft.com/fwlink/p/?LinkId=251831).

Parameters

-Identity [<SPSitePipeBind>]

Specifies the SPSite object to run upgrade operations against.

Required?   True
Position?   1
Default value?  
Accept pipeline input?   True
Accept wildcard characters?   False

-AssignmentCollection [<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.

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.

Required?   False
Position?   Named
Default value?  
Accept pipeline input?   True
Accept wildcard characters?   False

-Confirm [<SwitchParameter>]

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

Required?   False
Position?   Named
Default value?  
Accept pipeline input?   False
Accept wildcard characters?   False

-Email [<SwitchParameter>]

Specifies whether to send mail on completion of the site collection upgrade.

Required?   False
Position?   Named
Default value?  
Accept pipeline input?   False
Accept wildcard characters?   False

-QueueOnly [<SwitchParameter>]

Required?   False
Position?   Named
Default value?  
Accept pipeline input?   False
Accept wildcard characters?   False

-Unthrottled [<SwitchParameter>]

Specifies a farm administrator to bypass the throttle which permits a site collection to be upgraded even if there are "too many" site collections in the throttle to be upgraded.

Required?   False
Position?   Named
Default value?  
Accept pipeline input?   False
Accept wildcard characters?   False

-VersionUpgrade [<SwitchParameter>]

Specifies to perform a version-to-version upgrade on the SPSite object. When this parameter is set, it internally triggers all available build-to-build actions that are associated with the current site collection operating mode. Version-to-version actions follow to bring site collections to the next site collection operating mode inclusive of all new build-to-build actions that are associated with the new site collection operating mode. When this parameter is not set, it triggers only available build-to-build upgrade actions that are associated with the current site collection operating mode.

Required?   False
Position?   Named
Default value?  
Accept pipeline input?   False
Accept wildcard characters?   False

-WhatIf [<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

Required?   False
Position?   Named
Default value?  
Accept pipeline input?   False
Accept wildcard characters?   False

Notes

Examples

EXAMPLE 1

PS> C:\PS>Upgrade-SPSite http://<site name>/sites/testsite

This example upgrades the existing http://<site name>/sites/testsite site collection by using only build-to-build upgrade actions. The SPSite.CompatibilityLevel will not be changed by this operation.

EXAMPLE 2

PS> C:\PS>Upgrade-SPSite http://<site name>/sites/testsite -VersionUpgrade

This example upgrades the existing http://<site name>/sites/testsite site collection by using only build-to-build upgrade actions. The SPSite.CompatibilityLevel will not be changed by this operation.