Choose a database engine upgrade method
Applies to: SQL Server (all supported versions) - Windows only
There are several approaches to consider when you are planning to upgrade the Database Engine from a prior release of SQL Server in order to minimize downtime and risk. You can perform an upgrade in-place, migrate to a new installation, or perform a rolling upgrade. The following diagram will help you to choose amongst these approaches. Each of the approaches in the diagram are also discussed below. To assist you with the decision points in the diagram, please also review Plan and Test the Database Engine Upgrade Plan.
To download SQL Server, go to Evaluation Center.
Have an Azure account? Then go Here to spin up a Virtual Machine with SQL Server Developer Edition already installed.
You may also consider upgrading the Azure SQL Database or virtualizing your SQL Server environment as part of your upgrade plan. These articles are out of scope for this article, but here are some links:
With this approach, the SQL Server setup program upgrades the existing SQL Server installation by replacing the existing SQL Server bits with the new SQL Server bits and then upgrades each of the system and user databases. The upgrade in-place approach is easiest, requires some amount of downtime, takes longer to fallback if a fallback is necessary, and it is not supported for all scenarios. For more information on supported and unsupported upgrade in-place scenarios, see Supported Version and Edition Upgrades.
This approach is frequently used in the following scenarios:
A development environment without a high-availability (HA) configuration.
A non-mission critical production environment that can tolerate downtime and that is running on a recent hardware and software. The amount of downtime is dependent upon the size of your database and the speed of your I/O subsystem. Upgrading SQL Server 2014 when memory-optimized tables are in use will take some extra time. For more information, see Plan and Test the Database Engine Upgrade Plan.
For an example of how Microsoft has used this strategy, see the following blog post: To upgrade or not to upgrade.
When running the SQL Server setup program, the SQL Server instance is stopped and restarted as part of running the pre-upgrade checks.
When you upgrade SQL Server, the previous SQL Server instance will be overwritten and will no longer exist on your computer. Before upgrading, back up SQL Server databases and other objects associated with the previous SQL Server instance.
The following diagram provides a high-level overview of the steps required for an in-place upgrade of the Database Engine.
For detailed steps, see Upgrade SQL Server Using the Installation Wizard (Setup).
Migrate to a new installation
With this approach, you maintain the current environment while you build a new SQL Server environment, frequently on new hardware and with a new version of the operating system. After installing SQL Server in the new environment, you perform a number of steps to prepare the new environment so that you can migrate the existing user databases from the existing environment to the new environment and minimize downtime. These steps include migrating the following:
- System objects: Some applications depend on information, entities, and/or objects that are outside of the scope of a single user database. Typically, an application has dependencies on the master and msdb databases, and also on the user database. Anything stored outside of a user database that is required for the correct functioning of that database must be made available on the destination server instance. For example, the logins for an application are stored as metadata in the master database, and they must be re-created on the destination server. If an application or database maintenance plan depends on SQL Server Agent jobs, whose metadata is stored in the msdb database, you must re-create those jobs on the destination server instance. Similarly, the metadata for a server-level trigger is stored in master.
When you move the database for an application to another server instance, you must re-create all the metadata of the dependent entities and objects in master and msdb on the destination server instance. For example, if a database application uses server-level triggers, just attaching or restoring the database on the new system is not enough. The database will not work as expected unless you manually re-create the metadata for those triggers in the master database. For detailed information, see Manage Metadata When Making a Database Available on Another Server Instance (SQL Server)
Integration Services packages stored in MSDB: If you are storing packages in MSDB, you will need to either script out those packages using the dtutil Utility or redeploy them to the new server. Before using the packages on the new server, you will need to upgrade the packages to SQL Server. For more information, see Upgrade Integration Services Packages.
Reporting Services encryption keys: An important part of report server configuration is creating a backup copy of the symmetric key used for encrypting sensitive information. A backup copy of the key is required for many routine operations, and enables you to reuse an existing report server database in a new installation. For more information, see Back Up and Restore Reporting Services Encryption Keys and Upgrade and Migrate Reporting Services
Once the new SQL Server environment has the same system objects as the existing environment, you then migrate the user databases from the existing system to the SQL Server instance in a manner that will minimize downtime on the existing system. You accomplish the database migration either using backup and restore, or by repointing LUNs if you are in a SAN environment. The steps for both methods are delineated in the diagrams below.
The amount of downtime is dependent upon the size of your database and the speed of your I/O subsystem. Upgrading SQL Server 2014 when memory-optimized tables are in use will take some extra time. For more information, see Plan and Test the Database Engine Upgrade Plan.
After migrating the user database(s), you point new users to the new SQL Server instance using one of a variety of methods (e.g. renaming the server, using a DNS entry, modifying connection strings). The new installation approach reduces risk and downtime as compared to an in-place upgrade , and facilitates hardware and operating system upgrades in conjunction with the upgrade to SQL Server.
If you already have a high availability (HA) solution in place or some other multiple SQL Serverinstance environment, go Rolling upgrade. If you do not have a high availability solution in place, you can consider either temporarily configuring Database Mirroring to further minimize downtime to facilitate this upgrade or taking this opportunity to configure an Always On Availability Group as a permanent HA solution.
For example, you may use this approach to upgrade:
- An installation of SQL Server on an unsupported operating system.
- An x86 installation of SQL Server as SQL Server 2016 (13.x) and later do not support x86 installations.
- SQL Server to new hardware and/or a new version of the operating system.
- SQL Server in conjunction with server consolidation.
- SQL Server 2005 as SQL Server 2016 (13.x) and later do not support the in-place upgrade of SQL Server 2005. For more information, see Are you upgrading from SQL Server 2005.
The steps required for a new installation upgrade vary slightly depending upon whether you are using attached storage or SAN storage.
Attached storage environment: If you have a SQL Server environment using attached storage, the following diagram and the links within the diagram to guide you through the steps required for a new installation upgrade of the Database Engine.
SAN storage environment: If you have a SQL Server environment using SAN storage, the following diagram and the links within the diagram to guide you through the steps required for a new installation upgrade of the Database Engine.
A rolling upgrade is required in SQL Server solution environments involving multiple SQL Server instances that must be upgraded in a certain order to maximize uptime, minimize risk, and preserve functionality. A rolling upgrade is essentially the upgrade of multiple SQL Server instances in a particular order, either performing an upgrade in-place on each existing SQL Server instance or performing a new installation upgrade to facilitate upgrading hardware and/or the operating system as part of the upgrade project. There are a number of scenarios in which you need to use the rolling upgrade approach. These are documented in the following articles:
- Always-On Availability Groups: For detailed steps for performing a rolling upgrade in this environment, see Upgrading Always On Availability Group Replica Instances.
- Failover cluster instances: For detailed steps for performing a rolling upgrade in this environment, see Upgrade a SQL Server Failover Cluster Instance
- Mirrored instances: For detailed steps for performing a rolling upgrade in this environment, see Upgrading Mirrored Instances.
- Log shipping instances: For detailed steps for performing a rolling upgrade in this environment, see Upgrading Log Shipping for SQL Server (Transact-SQL).
- A replication environment: For detailed steps for performing a rolling upgrade in this environment, see Upgrade Replicated Databases.
- A SQL Server Reporting Services scale-out environment: For detailed steps for performing a rolling upgrade in this environment, see Upgrade and Migrate Reporting Services.