Skip to content

work-with-multiple-versions-and-instances-of-sql-server.md

Latest commit

 

History

History
122 lines (76 loc) · 9.73 KB

work-with-multiple-versions-and-instances-of-sql-server.md

File metadata and controls

122 lines (76 loc) · 9.73 KB
title Work with multiple versions and instances
ms.custom seo-lt-2019
ms.date 12/13/2019
ms.prod sql
ms.reviewer
ms.technology install
ms.topic conceptual
helpviewer_keywords
concurrent installations [SQL Server]
versions [SQL Server], multiple
side-by-side installations [SQL Server]
multiple SQL Server component versions
installing SQL Server, side-by-side installations
Setup [SQL Server], side-by-side installations
64-bit edition [SQL Server]
32-bit edition [SQL Server]
editions [SQL Server], side-by-side installations
ms.assetid 93acefa8-bb41-4ccc-b763-7801f51134e0
author MashaMSFT
ms.author mathoma

Work with multiple versions and instances of SQL Server

[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md-winonly]

You can install multiple instances of SQL Server, or install SQL Server on a computer where earlier SQL Server versions are already installed.

The following SQL Server-related items are compatible with the installation of multiple instances on the same computer:

  • Database Engine

  • Analysis Services

  • Reporting Services (in SQL Server 2016, and previous). Starting with SQL Server 2016. SQL Server Reporting Services (SSRS) has a separate installation.

You can upgrade earlier versions of SQL Server on a computer where other SQL Server versions are already installed. For supported upgrade scenarios, see Supported Version and Edition Upgrades.

Version Components and Numbering

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.

Components shared across minor versions

[!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.

The following table shows side-by-side support for each version of SQL Server on commonly supported versions of Windows:

Existing instance Side by side support
SQL Server 2019 SQL Server 2008 through SQL Server 2017
SQL Server 2017 SQL Server 2008 through SQL Server 2016
SQL Server 2016 SQL Server 2008 through SQL Server 2014

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.

SQL Server 2016 and greater 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.

Preventing IP Address Conflicts

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.

See Also