Migrate-SPProjectDatabase

Copies the data from the Project Server 2013 database into the corresponding SharePoint Server 2016 content database containing the migrated site collection.

Syntax

Migrate-SPProjectDatabase
       [-AssignmentCollection <SPAssignmentCollection>]
       [-Confirm]
       -DatabaseName <String>
       [-DatabaseServer <String>]
       [-FailoverPartner <String>]
       [-Overwrite]
       [-SQLLogon <PSCredential>]
       -SiteCollection <SPSitePipeBind>
       [-WhatIf]
       [<CommonParameters>]

Description

Copies the data from the Project Server 2013 database into the corresponding SharePoint Server 2016 content database containing the migrated site collection.

Both the Project Server 2013 database and the SharePoint Server 2016 database must be on the same instance of SQL Server and the SharePoint farm account must have full access to the Project Server 2013 database. During the migration process the Project Server 2013 database will be modified and cannot be mounted back to a Project Server 2013.

Examples

Example 1

PS C:\>Migrate-SPProjectDatabase -Name ProjectDB1 -SiteCollection "http://contoso1/sites/PWA"

This example will look for a Project Server 2013 database named ProjectDB1 on the same instance of SQL Server where the content database containing http://contoso1/sites/PWA is located. The data will be upgraded and copied into the site collection.

Required Parameters

-DatabaseName

The name of the Project Server 2013 database.

Type:String
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False
Applies to:Project Server 2016
-SiteCollection

The URL of the site collection to which you want to copy the Project data.

Type:SPSitePipeBind
Position:Named
Default value:None
Accept pipeline input:True (ByValue)
Accept wildcard characters:False
Applies to:Project Server 2016

Optional Parameters

-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, 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.

Type:SPAssignmentCollection
Position:Named
Default value:None
Accept pipeline input:True (ByValue)
Accept wildcard characters:False
Applies to:Project Server 2016
-Confirm

Prompts you for confirmation before running the cmdlet.

Type:SwitchParameter
Aliases:cf
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False
Applies to:Project Server 2016
-DatabaseServer

The name of the instance of SQL Server hosting the Project Server 2013 database.

Type:String
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False
Applies to:Project Server 2016
-FailoverPartner

The name of the SQL Server failover partner for the Project Server 2013 database.

Type:String
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False
Applies to:Project Server 2016
-Overwrite

Specifies to overwrite any Project data from previous attempts.

Type:SwitchParameter
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False
Applies to:Project Server 2016
-SQLLogon

SQL Server authentication credentials if needed.

Type:PSCredential
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False
Applies to:Project Server 2016
-WhatIf

Shows what would happen if the cmdlet runs. The cmdlet is not run.

Type:SwitchParameter
Aliases:wi
Position:Named
Default value:None
Accept pipeline input:False
Accept wildcard characters:False
Applies to:Project Server 2016

Inputs

Microsoft.SharePoint.PowerShell.SPSitePipeBind

Microsoft.SharePoint.PowerShell.SPAssignmentCollection

Outputs

System.Object