Updating sql server 2016
Using best practices on the legacy SQL Server systems first will help ensure a smoother upgrade.Then work though the SQL Server 2016 Upgrade Advisor tasks, review deprecated features and any blocking issues that need to be resolved prior to upgrade.
You must back up your MDS and DQS databases before upgrading to prevent any accidental data loss.(Note: Microsoft did not create a SQL Server 2016 version.The 2014 version guide should be similar enough for this purpose.) To get a sense for what might be entailed in the upgrade process in your environment, you will want work through an assessment your environment.In SQL Server 2016 , those applications do have schema upgrade level changes.After upgrading to SQL Server 2016, any earlier version of the Add-Ins for Excel will no longer work.For Analysis Services, be sure to check the known problems and workarounds before you upgrade in the SQL Server 2016 Release Notes especially since Upgrade Advisor is missing Analysis Services this version.
Analysis Services Backward Compatibility summarizes discontinued, deprecated, and changed features.
You will need to migrate packages afterward service upgrade completes with the Integration Services Package Upgrade Wizard.
Developers can upgrade 2012 or 2014 projects to 2016 without manual adjustments after upgrade.
The SQL Server Setup program will not perform that task.
Rolling upgrade Last but not least, you may need to consider a rolling upgrade if your environment has multiple SQL Server instances that need to be upgraded in a specific order to maximize uptime, minimize risk, and preserve functionality.
Unless you have a personal instance, most real-world SQL Server environments can be complex to upgrade.