In one of his articles written after the conference, Microsoft TechEd 2013 North America, I mentioned that we have entered a new world of services, Microsoft «free versions.» This is evident from the annual update cycle of Windows 8, Windows Server, Visual Studio, SQL Server and all other products. One of the main conditions for peace «no version» — a seamless upgrade process to be able to move, for example, SharePoint 2010, SharePoint 2013 or to between versions of Office 365.
Improvements in the process of an upgrade to SharePoint
«Technical» the update process with the transition from SharePoint 2010, SharePoint 2013 to markedly improved. You’re last «in-place upgrade» is rarely beneficial. Now the user builds a new SharePoint farm in 2013 and acceding to the content databases and service applications. When you attach a database to the farm 2013 2010 database is updated. However, the actual site collection continues to function in a mode 2010 to until a farm administrator or site collection will not update them. After that they get the appropriate form and are site collections 2013. This approach is known as «deferred» (deferred) update site collection.
Deferred update site collection is markedly different from the visual upgrade in the transition from SharePoint 2007 to 2010. In the case of renewed family of Web sites, but you can use visualization to end users, they still looked like a family of Web sites in 2007 . However, the main page is in reality a family of Web sites in 2010, which meant that the consumer must first find and fix any problems preventing the upgrade.