| title | Work with Multiple Versions and Instances of SQL Server | Microsoft Docs | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ms.custom | ||||||||||
| ms.date | 08/25/2017 | |||||||||
| ms.prod | install | |||||||||
| ms.prod_service | sql-non-specified | |||||||||
| ms.service | database-engine | |||||||||
| ms.component | ||||||||||
| ms.reviewer | ||||||||||
| ms.suite | sql | |||||||||
| ms.technology |
|
|||||||||
| ms.tgt_pltfrm | ||||||||||
| ms.topic | article | |||||||||
| helpviewer_keywords |
|
|||||||||
| ms.assetid | 93acefa8-bb41-4ccc-b763-7801f51134e0 | |||||||||
| caps.latest.revision | 67 | |||||||||
| author | MikeRayMSFT | |||||||||
| ms.author | mikeray | |||||||||
| manager | jhubbard | |||||||||
| ms.workload | Active |
[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md] [!INCLUDEssNoVersion] supports multiple instances of the [!INCLUDEssDE], [!INCLUDEssASnoversion], and [!INCLUDEssRSnoversion] on the same computer. You can also upgrade earlier versions of [!INCLUDEssNoVersion], or install [!INCLUDEssNoVersion] on a computer where earlier [!INCLUDEssNoVersion] versions are already installed. For supported upgrade scenarios, see Supported Version and Edition Upgrades.
The following concepts are useful in understanding the behavior of [!INCLUDEssNoVersion] for side-by-side instances of [!INCLUDEssNoVersion].
The standard product version format for [!INCLUDEssNoVersion] is MM.nn.bbbb.rr where each segment is defined as:
MM - Major version
nn - Minor version
bbbb - Build number
rr - Build revision number
In each major or minor release of [!INCLUDEssNoVersion], there is an increment to the version number to differentiate it from earlier versions. This change to the version is used for many purposes. This includes displaying version information in the user interface, controlling how files are replaced during upgrade, applying service packs, and also as a mechanism for functional differentiation between the successive versions.
Components shared by all versions of [!INCLUDEssNoVersion]
Certain components are shared by all instances of all installed versions of [!INCLUDEssNoVersion]. When you install different versions of [!INCLUDEssNoVersion] side-by-side on the same machine, these components are automatically upgraded to the latest version. Such components are usually uninstalled automatically when the last instance of [!INCLUDEssNoVersion] is uninstalled.
Examples: [!INCLUDEssNoVersion] Browser and Microsoft [!INCLUDEssNoVersion] VSS Writer.
Components shared across all instances of the same major version of [!INCLUDEssNoVersion]
[!INCLUDEssNoVersion] versions that have the same major version share some components across all instances. If the shared components are selected during upgrade, the existing components are upgraded to the latest version.
Examples: [!INCLUDEssISnoversion], [!INCLUDEssMDSshort], [!INCLUDEssManStudioFull], [!INCLUDEssBIDevStudioFull], and [!INCLUDEssNoVersion] Books Online.
[!INCLUDEssNoVersion] versions that have the same major.minor version shared components.
Example: Setup support files.
Components specific to an instance of [!INCLUDEssNoVersion]
Some [!INCLUDEssNoVersion] components or services are specific to an instance of [!INCLUDEssNoVersion]. These are also known as instance-aware. They share the same version as the instance that hosts them, and are used exclusively for that instance.
Examples: [!INCLUDEssDE], [!INCLUDEssASnoversion], and [!INCLUDEssRSnoversion].
Components that are independent of the [!INCLUDEssNoVersion] versions
Certain components are installed during [!INCLUDEssNoVersion] setup, but are independent of the versions of [!INCLUDEssNoVersion]. They may be shared across major versions or by all [!INCLUDEssNoVersion] versions.
Examples: Microsoft Sync Framework, [!INCLUDEssNoVersion] Compact.
For more information about [!INCLUDEssNoVersion] Compact installation, see Install SQL Server 2016 from the Installation Wizard (Setup). For more information about how to uninstall [!INCLUDEssNoVersion] Compact, see Uninstall an Existing Instance of SQL Server (Setup).
Using [!INCLUDEssNoVersion] Side-By-Side with Previous Versions of [!INCLUDEssNoVersion]
You can install [!INCLUDEssNoVersion] on a computer that is already running instances of an earlier [!INCLUDEssNoVersion] version. If a default instance already exists on the computer, [!INCLUDEssNoVersion] must be installed as a named instance.
Caution
[!INCLUDEssNoVersion] SysPrep does not support side by side installation of prepared instances of [!INCLUDEssCurrent] with earlier versions of [!INCLUDEssNoVersion] on the same computer. For example, you cannot prepare a [!INCLUDEssCurrent] instance side by side with a prepared instance of [!INCLUDEssSQL11]. However, you can install multiple prepared instances of the same major version of [!INCLUDEssNoVersion] side by side on the same computer. For more information, see Considerations for Installing SQL Server Using SysPrep.
[!INCLUDEssCurrent] cannot be installed side-by-side with earlier versions of [!INCLUDEssNoVersion] on a computer that is running Windows Server 2008 R2 Server Core SP1. For more information on Server Core installations, see Install SQL Server 2016 on Server Core.
The following table shows side-by-side support for [!INCLUDEssCurrent]:
| Existing instance of [!INCLUDEssCurrent] | Side-by-side support |
|---|---|
| [!INCLUDEssCurrent] (64-bit) [!INCLUDEvcprx64] | [!INCLUDEssVersion2005] (32-bit) [!INCLUDEssVersion2005] (64-bit) [!INCLUDEvcprx64] [!INCLUDEssKatmai] (32-bit) [!INCLUDEssKatmai] (64-bit) [!INCLUDEvcprx64] [!INCLUDEssKilimanjaro] (32-bit) [!INCLUDEssKilimanjaro] (64-bit) [!INCLUDEvcprx64] [!INCLUDEssSQL11] (32-bit) [!INCLUDEssSQL11] (64-bit) [!INCLUDEvcprx64] [!INCLUDEssSQL14] (32-bit) [!INCLUDEssSQL14] (64-bit) [!INCLUDEvcprx64] [!INCLUDEssSQL15] |
The following table shows side-by-side support for [!INCLUDEssSQL15] with previous versions:
| Existing instance of [!INCLUDEssSQL15] | Side-by-side support for previous versions |
|---|---|
| [!INCLUDEssSQL15] [!INCLUDEvcprx64] | [!INCLUDEssVersion2005] (32-bit) [!INCLUDEssVersion2005] (64-bit) [!INCLUDEvcprx64] [!INCLUDEssKatmai] (32-bit) [!INCLUDEssKatmai] (64-bit) [!INCLUDEvcprx64] [!INCLUDEssKilimanjaro] (32-bit) [!INCLUDEssKilimanjaro] (64-bit) [!INCLUDEvcprx64] [!INCLUDEssSQL11] (32-bit) [!INCLUDEssSQL11] (64-bit) [!INCLUDEvcprx64] [!INCLUDEssSQL14] (32-bit) [!INCLUDEssSQL14] (64-bit) [!INCLUDEvcprx64] |
When a [!INCLUDEssNoVersion] Failover Cluster Instance is installed side-by-side with a standalone instance of the [!INCLUDEssDEnoversion], take care to avoid TCP port number conflicts on the IP addresses. Conflicts usually occur when two instances of the [!INCLUDEssDE] are both configured to use the default TCP port (1433). To avoid conflicts, configure one instance to use a non-default fixed port. Configuring a fixed port is usually easiest on the standalone instance. Configuring the [!INCLUDEssDE] to use different ports will prevent an unexpected IP Address/TCP port conflict that blocks an instance startup when a [!INCLUDEssNoVersion] Failover Cluster Instance fails to the standby node
Hardware and Software Requirements for Installing SQL Server
Install SQL Server from the Installation Wizard (Setup)
Supported Version and Edition Upgrades
Upgrade SQL Server
Editions and supported features of SQL Server 2017
Editions and supported features of SQL Server 2016
Backward Compatibility_deleted