Forum Discussion
Slow Mount Times and Upgrade Failures During SharePoint 2013 to 2016 Migration
Hi everyone, I'm seeking advice on some challenges I'm facing while migrating a SharePoint 2013 farm to SharePoint 2016. Initial Setup: Successfully configured a SharePoint 2016 farm with attache...
Hello Nicolas thank you for your response i was getting above error for one one content db which say id not found and we are on sql 2019
Okey! I think this is the best way for you to handle this as it's probably going to be faster for you and less of an headace!
Create a new Content Database on the Web Application, then use Move-SPSite to migrate each Site Collection to the new database.
Create a new Content Database on the Web Application, then use Move-SPSite to migrate each Site Collection to the new database.