So, if you've decided to make the jump to SQL Server 2016, what's the best way to ensure a fast and smooth upgrade?There are two basic strategies for upgrading to the new release: Each method has its advantages and disadvantages.Plus, in many instances, you'll also be implementing a new version of Windows Server, something that requires a new operating system license.When you are planning an upgrade to a new version of SQL Server, it is not always obvious what obstacles you might encounter during the actual upgrade.here, a 10-minute Channel 9 video here, and the updated edition feature comparison here.The latest Cumulative Update can always be obtained from the Download Center (older builds can be obtained from the Microsoft Update Catalog).However, this version is completely different from its predecessors, and is available in preview from today - long before the release of SQL Server 2016!In addition, there is a new feature available here, called the Stretch Database Advisor, which will help provide guidance about tables that might be good candidates for this new SQL Server 2016 feature.
The end result is a more stable new installation of SQL Server.
With a clean upgrade, the database also can remain available on the original system while you perform the install on a new one.
However, this method is time-consuming and tends to be more costly, because you need to back up and restore all of your databases.
Because of the change from socket to core, in-place upgrades may come with a hefty cost increase.
Microsoft enhanced SQL Server security with the new Always Encrypted, row-level security and dynamic data asking features.
To try to explain here, CU3 was officially released on November 16th, but the security update that was released on November 8th actually already included all of the fixes in the CU.