Export (0) Print
Expand All

Migrate PowerPivot to SharePoint 2013

  

SharePoint 2013 does not support in-place upgrade. However the procedure of database-attach upgrade is supported. The behavior is different from upgrading to SharePoint 2010, where a customer could choose between the two basic upgrade approaches, in-place upgrade and database-attach upgrade.

If you have a PowerPivot for SharePoint installation integrated with SharePoint 2010, you cannot upgrade in-place the SharePoint server. However you can migrate content databases and service application databases from the SharePoint 2010 farm to a SharePoint 2013 farm. This topic is an overview of the steps required to complete a database-attach upgrade and complete a migration related to PowerPivot:

Applies to: SharePoint 2013

Migration Overview

1

2

3

4

Prepare the SharePoint 2013 farm

Backup, copy, restore databases.

Mount content databases

Migrate PowerPivot Schedules

SQL Server Management Studio

  • SharePoint Central Administration

  • Windows PowerShell

  • SharePoint application Pages

  • Windows PowerShell

  

In this topic:

  1. Tip Tip

    Review the authentication method your existing web applications are configured for. SharePoint 2013 web applications default to claims-based authentication. SharePoint 2010 web applications configured for classic-mode authentication require additional steps to migrate databases from SharePoint 2010 to SharePoint 2013. If your web applications are configured for classic-mode authentication, review the SharePoint 2013 documentation.

  2. Install a new SharePoint Server 2013 farm.

  3. Install an instance of a SQL Server 2014 Analysis Services server in SharePoint mode. For more information, see PowerPivot for SharePoint 2013 Installation.

  4. Run the PowerPivot for SharePoint 2013 installation package spPowerPivot.msi on each server in the SharePoint farm. For more information, see Install or Uninstall the PowerPivot for SharePoint Add-in (SharePoint 2013).

  5. In SharePoint 2013 Central Administration, configure the Excel Services service application to use the Analysis Services SharePoint mode server created in the previous step. For more information, see the “Configure Basic Analysis Services SharePoint Integration” section of PowerPivot for SharePoint 2013 Installation.

Arrow icon used with Back to Top link Top

The “SharePoint database-attach upgrade” process is a sequence of steps to back up, copy, and restore PowerPivot related content and service application databases to the SharePoint 2013 farm.

  1. Set Database to read-only: In SQL Server Management Studio, right-click the database name and click Properties. On the Options page, set the Database read-Only property to True.

  2. Back up: Back up each content database and service application database that you want to migrate to the SharePoint 2013 farm. In SQL Server Management Studio, right-click the database name, click Tasks, and click Back up.

  3. File copy the database backup files (.bak) to the desired destination server.

  4. Restore: Restore the databases to the destination SQL Server Database Engine. This step can be completed using SQL Server Management Studio.

  5. Set Database to read-write: Set the Database read-Only to False.

Arrow icon used with Back to Top link Top

For a more detailed explanation of the following procedures, see Upgrade databases from SharePoint 2010 to SharePoint 2013 (http://go.microsoft.com/fwlink/p/?LinkId=256690).

  1. Take Databases Offline:

    Take each SharePoint 2013 content database offline, using SharePoint Central Administration. The content databases are replaced by the databases you copied over. Consider what is the best sequence for your environment. Consider taking each database offline and mount its relevant replacement database before taking the next content database offline. Another option is to take all the content databases offline as a group.

    1. In SharePoint Central Administration, click Application Management.

    2. Click Manage Content Databases.

    3. Click the name of the database.

    4. On the Manage Content Database Settings, set Database status to Offline.

    5. Select Remove Content Database. Note the warning that sites stored in the content database will no longer be accessible.

  • Mount content databases:

    Use PowerShell cmdlets in the SharePoint 2013 Management shell to mount the migrated content database. The service application database does not need to be mounted, only the content databases: PowerShell related content

    Mount-SPContentDatabase "SharePoint_Content_O14-KJSP1" -DatabaseServer "[server name]\powerpivot" -WebApplication [web application URL]
    

    For more information, see Attach or detach content databases (SharePoint Server 2010) (http://technet.microsoft.com/en-us/library/ff628582.aspx).

    Status when the step is complete: When the mount operation is complete, users can see files that were in the old content database. Therefore users can see and open the workbooks in the document library.

    • TipTip

      It is possible at this point in the migration process to create new schedules for the migrated workbooks. However, the schedules are created in the new PowerPivot service application database, and not the database you copied from the old SharePoint farm. Therefore it will not contain any of the old schedules. After you complete the following steps to use the old database and migrate the old schedules, the new schedules are not available.

Troubleshoot issues when you attempt to mount databases

This section summarizes possible issues encountered when mounting the database.

  1. Authentication errors: If you see errors related to authentication, review what authentication mode the source web applications are using. The error could be caused by a mismatch in authentication between the SharePoint 2013 web application and the SharePoint 2010 web application. See the Prepare the SharePoint 2013 Farm for more information.

  2. Missing PowerPivot.Files: If you see errors related to missing PowerPivot .dlls, the spPowerPivot.msi has not been installed or the PowerPivot Configuration Tool has not been used to configure PowerPivot.

This section describes the details and options for migrating PowerPivot schedules. Schedule migration is a two-step process. First configure the PowerPivot service application to use the migrated service application database. Second, choose one of two options for schedule migration.

Configure the service application to use the migrated service application database.

In SharePoint Central Administration to configure the PowerPivot services application to use the old service application database you copied over. The PowerPivot Service upgrades the service application database to the new schema.

  1. In SharePoint Central Administration, click Manage Service Applications.

  2. Find the PowerPivot service application, for example “Default PowerPivot Service Application”, click the name of the service application and click Properties in the SharePoint ribbon.

  3. Update the database server name-instance and the database name. To the correct names for the database you backed up, copied, and restored. Once you click Ok, the service application database is upgraded. Errors will be in the ULS log.

Upgrade PowerPivot schedules

Configure the PowerPivot service application to migrate refresh schedules.

  • Migrate Schedules option1: SharePoint farm administrator

    1. In the SharePoint 2013 Management Run the Set-PowerPivotServiceApplication cmdlet with the -StartMigratingRefreshSchedules switch to enable automatic on demand schedule migration PowerShell related content. The following Windows PowerShell script assumes that there is only one PowerPivot service application.

      $app=Get-PowerPivotServiceApplication
      Set-PowerPivotServiceApplication $app -StartMigratingRefreshSchedules
      

      After the Windows PowerShell script is run, the schedules are active and the schedules will run at the next appropriate time. However, the status one the schedule refresh page is not enabled. When the schedule runs the first time it will be migrated and on the schedule refresh page, Enabled will be true.

    2. If you want to check the current value of the StartMigratingRefreshSchedules property, run the following PowerShell script. The Script loops through all PowerPivot service application objects and display the name and property values:

      $apps = Get-PowerPivotServiceApplication
      foreach ($app in $apps){}
      Get-PowerPivotServiceApplication $appp | format-table -property displayname,id,StartMigratingRefreshSchedules
      

    Migrate Schedules option2: User updates each workbook

    1. Another option to migrate schedules is to enable the schedule refresh for each workbook. Navigate to the document library that contains the workbooks.

    2. Open the context menu and click Manage PowerPivot Data Refresh.

    3. In the schedule refresh section, click Enable.

    4. You can select Also refresh as soon as possible. This option adds one instance of the refresh to the queue as soon as you click ok. The regular refresh schedule still triggers at the appropriate time.

    5. Click Ok. The refresh history is now visible in the refresh page, the schedule will fire at the normal time.

SQL Server 2008 R2 PowerPivot workbooks

  • SQL Server 2008 R2 PowerPivot workbooks do not automatically upgrade when they are used in SQL Server 2012 SP1 PowerPivot for SharePoint 2013. After you migrate a content database containing the 2008 R2 workbooks, you can use the workbooks but the schedules do not upgrade.

  • For more information, see Upgrade Workbooks and Scheduled Data Refresh (SharePoint 2013).

Arrow icon used with Back to Top link Top

Note Note

For more information on PowerPivot and SharePoint database-attach upgrade, see the following:

Arrow icon used with Back to Top link Top

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft