"Upgrade-spsite -verionupgrade" command taking too much time to complete - Project server 2013 RRS feed

  • Question

  • Hi,

    We are upgrading from Project server 2010 to 2013, and in that process we run the command 

    "upgrade-spsite -identity http://..../pwa -versionupgrade" and this command has completed on 15% after 2 days (48 hours). The size of the contentdabase, which holds the PWA site is only 10 GB. The configuration of Project server 2013 and Database server is

    8 Cores and 16 GB for each server (this is a 2 tier environment), the OS is Windows 2012 and SQL version is 2012 Enterprise. On SQL box we have stopped SSIS, SSRS and SSAS services. Both servers are virtual servers.

    Please help me to speed-up this task and fix for this issue. Because I have found on internet that people have upgraded 250 GB of data is just 2 days.


    Meen Bamm

    Thursday, July 9, 2015 11:32 AM

All replies

  • Hi Meen, 

    Did you got any solution to this. I am facing the same issue.

    Thursday, December 17, 2015 7:40 PM
  • Hi Meen/Amit,

    Not so helpful response, but i can tell you that lately i came across a same situation while upgrading PS2010 to PS2013. tried every possible combination, and then eventually gave up on migrating project sites data and choose to went with an alternate solution (mainly filtered out majority of sites and manually migrated data using PS Scripts)

    I did posted this issue to one of the existing thread addressing about the the same issue, but never got a reply.

    So my suggestion would be to chalk down some alternate workable solution between the stakeholders. 


    Khurram Jamshed - MBA, PMP, MCTS, MCITP ( Blog, Twitter, Linkedin )
    If you found this post helpful, please “Vote as Helpful”. If it answered your question, please “Mark as Answer”.

    Monday, December 21, 2015 12:00 AM
  • I am facing same issue while upgrading Project server the PowerShell command "upgrade-spsite...-versionupgrade" tooks about 3 days time in dev environment...

    Microsoft support also not able to find the root cause of slow upgrade process.

    Please help.


    Y K Das

    Tuesday, May 2, 2017 9:48 AM
  • Next time you run, try clearing the SharePoint cache prior to running.

    THere are several versions to pick from.  I like the ones that clear cache with PowerShell.

    Here is one I found on codePlex.

    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Blog contains my field notes and SQL queries

    Tuesday, May 9, 2017 2:54 AM