These are notes from my first upgrade of SharePoint 2010 to SharePoint 2013. The purpose of the upgrade is to carry out an initial test upgrade to find any issues etc. I’m not replicating the environment in terms of server roles etc. everything is installed on one server with local SQL. I followed the steps outlined here: http://technet.microsoft.com/en-us/library/cc303436.aspx
This is part 2, part 1 can be found here, part 2 here, part 3 here, part 4 here and part 5 here.
Copy databases to the new farm for upgrade to SharePoint 2013
Reference: http://technet.microsoft.com/en-us/library/jj839720.aspx
As this is a test upgrade, don’t set the databases to read-only.
Backup all the SharePoint 2010 content databases and the databases for any service applications you’re going to upgrade. See part 1 for upgradeable service applications.
Copy the SharePoint 2010 database backups to the SharePoint 2013 SQL server.
Restore the SharePoint 2010 database backups on the SharePoint 2013 SQL server.
If upgrading SQL server versions, change the database compatibility level to match the new SQL server version.
Pingback: Upgrading SharePoint 2010 To SharePoint 2013 Part 3 | Richard Skinner
Pingback: Upgrading SharePoint 2010 To SharePoint 2013 Part 4 | Richard Skinner
Pingback: Upgrading SharePoint 2010 To SharePoint 2013 Part 5 | Richard Skinner
Pingback: Upgrading SharePoint 2010 To SharePoint 2013 Part 1 | Richard Skinner
Helpful article Richard !!!
Just a quick question –
Is it OK to RENAME the SA Databases and restore them because I am using the same Database Server?
I have two different front-end one for 2010 and other is for 2013 and both are pointing to same Database Server.
Yes you can rename the DBs, just use the new DB name when running the PowerShell commands referenced in the later posts in this series.