Hi all, 

I'm currently trying to restore a large SP2010 Content Database (~350GB) to SharePoint 2013 using Database Attach (Mount-SPContentDatabase with -NoB2BSiteUpgrade), and everytime I run the the upgrade the process gets stuck at the same 50% mark for days (The longest I left it running for was 3 days)

I have also noticed from the SQL DB side that a "OPEN CURSOR" command was the long running T-SQL command on the DB. 

Is there any recommendation on how to optimize the performance of upgrading the DB. 

Any help is appreciated. 

Cheers

Hi,

Have you looked at the Upgrade Log in the C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\LOGS ? Also, why don't you want Build to Build as you are doing a Version to Version upgrade. Have you looked at using Upgrade-SPContentDatabase? Example

Upgrade-SPContentDatabase WSS_Content_YourContentdb -NoB2BSiteUpgrade

Reference: http://technet.microsoft.com/en-us/library/ff607813.aspx

-Ivan

Hi Ivan, 

The logs are showing the following in the last steps:

SharePoint Foundation Upgrade SPContentDatabaseSequence ajy5n DEBUG Dropping all FN functions. e8e21810-e2de-4738-97f7-4bd3a2d6f863
SharePoint Foundation Upgrade SPContentDatabaseSequence ajyj8 DEBUG Executing SQL DDL Script. e8e21810-e2de-4738-97f7-4bd3a2d6f863
SharePoint Foundation Upgrade SPContentDatabaseSequence ajy5m DEBUG Dropping all TVF functions. e8e21810-e2de-4738-97f7-4bd3a2d6f863
SharePoint Foundation Upgrade SPContentDatabaseSequence ajyj8 DEBUG Executing SQL DDL Script. e8e21810-e2de-4738-97f7-4bd3a2d6f863

And as mentioned, the Mount-SPContentDatabase never errors or fails, it just hangs at that step above (With OPEN CURSOR at the SQL end)

We have also tried the following but with no luck:

Setting a max Memroy for the SQL
Set the Recovery Model to "Simple"

I use the -NoB2BSiteUpgrade because I would like to upgrade the DB without upgrading the Site Collection (So I can use the "deferred Site Upgrade")

could you please check via central admin if content DB attached to the farm?

make sure you have enough space on the sql server and you sql database is not caped?

before migrating i am sure you ran the test-spcontentdatabase in 2010, is there any error?

anything you can see in the ULS log?

The Content Database is NOT attached, and the DB shows "Upgrade in Progress" when I go to the "Check database Status" page in CA

I have free space more than double the size of the DB (Logs and Data)

Nothing in the ULS log, because the upgrade process did not fail, it is still in Progress. 

ok, do you have result from test-spcontenetdatbase command against the same db in s2010 farm?

one more thing, how many site collections in this content DB?

It is only 1 Site Collection. 

I have ran the Test-SPContentDatabase on the 2010DB in the SP2013 farm and had no BlockingErrors and only some Errors that are related to missing features. They should not block the upgrade. 

Is there anything specific that you want me to look in the test result?

UPDATE:

Just to let you know, that the upgrade job was still running until today (from the date I posted this) with no errors. 

• Edited by Ninos Yacoub Tuesday, November 12, 2013 3:43 AM

could you please share your upgrade log, from current upgrade....i want check it at what sequence it is hanging.

Every time I run the upgrade, it gets to this stage and hangs (Last Lines int he log below):

current object = [SPContentDatabase Name=SP2013_TEST_WSS_Content_80], current sequence = [SPContentDatabaseSequence], action 65 out of total 129

SPUpgradeSession ajxn2 DEBUG UPGRADE PERCENTAGE: 15.11627907% done

SPContentDatabaseSequence    ajyj8       DEBUG   Executing SQL DDL Script.

=================================================

11/05/2013 13:15:02.53 powershell (0x025C) 0x45D4 SharePoint Foundation Upgrade UpdateWebpartsIndex (15.0.75.0) ajywr DEBUG SQL Query Count=6 28815bc4-a382-447c-9f53-7a244029e8ec
11/05/2013 13:15:02.53 powershell (0x025C) 0x45D4 SharePoint Foundation Upgrade UpdateWebpartsIndex (15.0.75.0) ajywr DEBUG Execution Time=167.265392668621 28815bc4-a382-447c-9f53-7a244029e8ec
11/05/2013 13:15:02.53 powershell (0x025C) 0x45D4 SharePoint Foundation Upgrade UpdateWebpartsIndex (15.0.75.0) aloo1 DEBUG Exiting Upgrade Action 28815bc4-a382-447c-9f53-7a244029e8ec
11/05/2013 13:15:02.53 powershell (0x025C) 0x45D4 SharePoint Foundation Upgrade DropDocsCacheParseId (15.0.76.0) aloo0 DEBUG Entering Upgrade Action 28815bc4-a382-447c-9f53-7a244029e8ec
11/05/2013 13:15:02.53 powershell (0x025C) 0x45D4 SharePoint Foundation Upgrade SPUpgradeSession ajxn1 DEBUG UPGRADE PROGRESS: current object = [SPContentDatabase Name=SP2013_TEST_WSS_Content_80], current sequence = [SPContentDatabaseSequence], action 65 out of total 129 28815bc4-a382-447c-9f53-7a244029e8ec
11/05/2013 13:15:02.53 powershell (0x025C) 0x45D4 SharePoint Foundation Upgrade SPUpgradeSession ajxn2 DEBUG UPGRADE PERCENTAGE: 15.11627907% done, Total Elapsed Time 00:03:39.9702958. 28815bc4-a382-447c-9f53-7a244029e8ec
11/05/2013 13:15:02.64 powershell (0x025C) 0x45D4 SharePoint Foundation Upgrade DropDocsCacheParseId (15.0.76.0) ajywc DEBUG Begin Initialize() 28815bc4-a382-447c-9f53-7a244029e8ec
11/05/2013 13:15:02.64 powershell (0x025C) 0x45D4 SharePoint Foundation Upgrade DropDocsCacheParseId (15.0.76.0) ajywd DEBUG End Initialize() 28815bc4-a382-447c-9f53-7a244029e8ec
11/05/2013 13:15:02.64 powershell (0x025C) 0x45D4 SharePoint Foundation Upgrade DropDocsCacheParseId (15.0.76.0) ajywe INFO Drop Docs.CacheParseId and make Dirty calculated. 28815bc4-a382-447c-9f53-7a244029e8ec
11/05/2013 13:15:02.64 powershell (0x025C) 0x45D4 SharePoint Foundation Upgrade DropDocsCacheParseId (15.0.76.0) ajywf DEBUG Begin Upgrade() 28815bc4-a382-447c-9f53-7a244029e8ec
11/05/2013 13:15:02.64 powershell (0x025C) 0x45D4 SharePoint Foundation Upgrade DropDocsCacheParseId (15.0.76.0) ajyll DEBUG Dropping column AllDocs.CacheParseId 28815bc4-a382-447c-9f53-7a244029e8ec
11/05/2013 13:15:02.67 powershell (0x025C) 0x45D4 SharePoint Foundation Upgrade DropDocsCacheParseId (15.0.76.0) ajxhq DEBUG Dropping all FNs and TVFs due to dropping column AllDocs.CacheParseId 28815bc4-a382-447c-9f53-7a244029e8ec
11/05/2013 13:15:02.67 powershell (0x025C) 0x45D4 SharePoint Foundation Upgrade SPContentDatabaseSequence ajy5n DEBUG Dropping all FN functions. 28815bc4-a382-447c-9f53-7a244029e8ec
11/05/2013 13:15:02.67 powershell (0x025C) 0x45D4 SharePoint Foundation Upgrade SPContentDatabaseSequence ajyj8 DEBUG Executing SQL DDL Script. 28815bc4-a382-447c-9f53-7a244029e8ec
11/05/2013 13:15:02.92 powershell (0x025C) 0x45D4 SharePoint Foundation Upgrade SPContentDatabaseSequence ajy5m DEBUG Dropping all TVF functions. 28815bc4-a382-447c-9f53-7a244029e8ec
11/05/2013 13:15:02.92 powershell (0x025C) 0x45D4 SharePoint Foundation Upgrade SPContentDatabaseSequence ajyj8 DEBUG Executing SQL DDL Script. 28815bc4-a382-447c-9f53-7a244029e8ec

Hi Ninos,

I have successfully upgraded a 100GB ContentDb but would be hesitant to upgrade a Site Collection of 350GB and I would only do so as an experiment in DEV. Also, as I am sure you are aware the recommended size of ContentDbs should be less than 200GB. However, before we discuss SharePoint 2010 / 2013 software boundaries. Lets find out what HW you are attempting this upgrade on...

Are you using VMs, if so at what layer,

How much memory do you have on your WFE, APP and SQL Server. What

To help ensure system performance, we recommended that you limit the size of content databases to 200 GB, except when specific usage scenarios and conditions support larger sizes. For more information about content database size limits, see the Content database limits section in Software boundaries and limits for SharePoint 2013.

We generally recommend that a site collection should not exceed 100 GB unless it is the only site collection in the database so that you can use the SharePoint Server 2013 granular backup tools to move a site collection to another database if you need to.

If you still need to perform the upgrade one of the steps you should take with the DB while in your SharePoint 2010 environment is to add a couple ContentDbs, set them to warn on 1 Site Collection, with a MAX of 2 Site Collections, Create additional Site Collections, then move Content from your existing Site Collection into two or more Site Collection that have been created in their own ContentDbs.

As I mentioned previously this should only be a development exercise or learning experience. You should be using Migration Tools to migrate the amount of Content your talking about like metalogix or metaviz I would not recommend to anyone to perform an upgrade... There arte many issues beyond the upgrade that may haunt you..

Reference: Here is a list of tools http://www.topsharepoint.com/content-migration-tools-for-sharepoint

 

-Ivan

since last 7 days its still running and only 15% completed that's not acceptable. As Ivan suggest, try that approach, if you have multiple susbsites in your Site collection, move each or larger subsites to different site collection in different DB, then migrate all content DB to 2013.

Honestly, we have very large farm with more than 16TB data but none of our site collection cross 100GB, we have around 700 content db across multiple farms.

i think its best time to breakdown your site collection into multiple sites.lets say if you have a subsite for each department, may be think to give them a site collection.

 

Hi,

Did you guys resolve this issue

If so then how?

Since i am getting exactly the same issue as yours

"Dropping all FNs and TVFs due to dropping column AllDocs"

Please help !!!