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.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.For those folks running SQL Server 2000 instances (yes we KNOW you still exist) you are not able to upgrade directly to SQL Server 2016 without first upgrading to an intermediary version.Starting with SQL Server 2012 licensing is done per-core, not per-socket.
Once installed, you will find "Microsoft SQL Server 2016 Upgrade Advisor" in your Start menu.If you’re like most data professionals, your response probably included something along the lines of, “it’s difficult” and “everything breaks.” Yes, when it comes to upgrading a database server, there is a lot of uncertainty.With data and databases being the most critical asset that any company has, it’s easy to understand why we always want to be extra cautious with regards to upgrades. ” is the first question whenever an upgrade project is talked about.In previous major releases of SQL Server, the Upgrade Advisor tool has been made available only shortly before, or along with, the release of the new version, making it hard to use this resource to plan an upgrade very far in advance.As with previous releases, there is once again an Upgrade Advisor for SQL Server 2016.
For this post, we will look at the pre-upgrade checklist items you should consider before upgrading to SQL Server 2016. Trust me when I tell you that the extra legwork now will save you headaches later.