| title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.custom | ms.topic | helpviewer_keywords | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Work with multiple versions and instances |
You can install multiple instances of SQL Server or install SQL Server on a computer where earlier SQL Server versions are already installed. |
rwestMSFT |
randolphwest |
09/27/2023 |
sql |
install |
linux-related-content |
conceptual |
|
[!INCLUDE SQL Server -Windows Only]
You can install multiple instances of [!INCLUDE ssNoVersion], or install [!INCLUDE ssNoVersion] on a computer where earlier [!INCLUDE ssNoVersion] versions are already installed.
Note
If you need to install multiple instances of [!INCLUDE ssnoversion-md] on Linux, see Deploy and connect to SQL Server Linux containers.
The following [!INCLUDE ssNoVersion]-related items are compatible with the installation of multiple instances on the same computer:
- Database Engine
- Analysis Services
- Reporting Services 1
1 Starting with [!INCLUDE sssql16-md], [!INCLUDE ssNoVersion] Reporting Services (SSRS) is installed separately.
You can upgrade earlier versions of [!INCLUDE ssNoVersion] on a computer where other [!INCLUDE ssNoVersion] versions are already installed. For supported upgrade scenarios, see Supported Version and Edition Upgrades.
The following concepts are useful in understanding the behavior of [!INCLUDE ssNoVersion] for side-by-side instances of [!INCLUDE ssNoVersion].
The standard product version format for [!INCLUDE ssNoVersion] is MM.nn.bbbb.rr, where each segment is defined as:
MM- Major versionnn- Minor versionbbbb- Build numberrr- Build revision number
In each major or minor release of [!INCLUDE ssNoVersion], there's an increment to the version number to differentiate it from earlier versions. This change to the version is used for many purposes, including:
- displaying version information in the user interface
- controlling how files are replaced during upgrade
- applying service packs and cumulative updates
- as a mechanism for functional differentiation between the successive versions
Certain components are shared by all instances of all installed versions of [!INCLUDE ssNoVersion]. When you install different versions of [!INCLUDE ssNoVersion] 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 [!INCLUDE ssNoVersion] is uninstalled.
Examples: [!INCLUDE ssNoVersion] Browser and Microsoft [!INCLUDE ssNoVersion] VSS Writer.
[!INCLUDE ssNoVersion] 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: [!INCLUDE ssISnoversion], [!INCLUDE ssMDSshort], [!INCLUDE ssManStudioFull], [!INCLUDE ssBIDevStudioFull], and [!INCLUDE ssNoVersion] Books Online.
[!INCLUDE ssNoVersion] versions that have the same major.minor version shared components.
Example: Setup support files.
Some [!INCLUDE ssNoVersion] components or services are specific to an instance of [!INCLUDE ssNoVersion] (instance-aware). They share the same version as the instance that hosts them, and are used exclusively for that instance.
Examples: [!INCLUDE ssDE], [!INCLUDE ssASnoversion], and [!INCLUDE ssRSnoversion].
[!INCLUDE editions-supported-features-windows]
[!INCLUDE editions-supported-features-linux]
Certain components are installed during [!INCLUDE ssNoVersion] setup, but are independent of the versions of [!INCLUDE ssNoVersion]. They may be shared across major versions or by all [!INCLUDE ssNoVersion] versions.
Examples: Microsoft Sync Framework, [!INCLUDE ssNoVersion] Compact.
For more information about [!INCLUDE ssNoVersion] Compact installation, see Install SQL Server from the Installation Wizard (Setup). For more information about how to uninstall [!INCLUDE ssNoVersion] Compact, see Uninstall an existing instance of SQL Server (Setup).
You can install [!INCLUDE ssNoVersion] on a computer that is already running instances of an earlier [!INCLUDE ssNoVersion] version. If a default instance already exists on the computer, [!INCLUDE ssNoVersion] must be installed as a named instance.
The following table shows side-by-side support for each version of [!INCLUDE ssNoVersion] on commonly supported versions of Windows with required versions of .NET installed:
| Existing instance | Side by side support |
|---|---|
| [!INCLUDE sssql22-md] | [!INCLUDE sql2008-md] through [!INCLUDE sssql19-md] |
| [!INCLUDE sssql19-md] | [!INCLUDE sql2008-md] through [!INCLUDE sssql17-md] |
| [!INCLUDE sssql17-md] | [!INCLUDE sql2008-md] through [!INCLUDE sssql16-md] |
| [!INCLUDE sssql16-md] | [!INCLUDE sql2008-md] through [!INCLUDE sssql14-md] |
For more information, see Using SQL Server in Windows 8 and later.
[!INCLUDE ssNoVersion] SysPrep doesn't support side by side installation of prepared instances of [!INCLUDE ssnoversion] with earlier versions of [!INCLUDE ssNoVersion] on the same computer. However, you can install multiple prepared instances of the same major version of [!INCLUDE ssNoVersion] side by side on the same computer. For more information, see Considerations for Installing SQL Server Using SysPrep.
[!INCLUDE sssql16-md] and later versions can't be installed side-by-side with earlier versions of [!INCLUDE ssNoVersion] on a computer that is running [!INCLUDE winserver2008r2-md] Server Core SP 1. For more information on Server Core installations, see Install SQL Server on Server Core.
When a [!INCLUDE ssNoVersion] Failover Cluster Instance is installed side by side with a standalone instance of the [!INCLUDE ssDEnoversion], take care to avoid TCP port number conflicts on the IP addresses. Conflicts usually occur when two instances of the [!INCLUDE ssDE] 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 [!INCLUDE ssDE] to use different ports prevents an unexpected IP address/TCP port conflict that blocks an instance startup when a [!INCLUDE ssNoVersion] Failover Cluster Instance fails to the standby node.