Skip to content

replication-backward-compatibility.md

Latest commit

 

History

History
51 lines (40 loc) · 2.94 KB

replication-backward-compatibility.md

File metadata and controls

51 lines (40 loc) · 2.94 KB
title Replication Backward Compatibility | Microsoft Docs
ms.custom
ms.date 03/02/2016
ms.prod sql
ms.prod_service database-engine
ms.reviewer
ms.technology replication
ms.topic conceptual
helpviewer_keywords
transactional replication, backward compatibility
backward compatibility [SQL Server replication]
merge replication backward compatibility [SQL Server replication]
replication [SQL Server], backward compatibility
backward compatibility [SQL Server], replication
snapshot replication [SQL Server], backward compatibility
compatibility [SQL Server replication]
ms.assetid 091c51dc-8b32-4b4f-847e-b317456c8394
author MashaMSFT
ms.author mathoma
monikerRange =azuresqldb-mi-current||>=sql-server-2016||=sqlallproducts-allversions

Replication Backward Compatibility

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

Backward compatibility is important to understand if you are upgrading, or if you have more than one version of SQL Server in a replication topology.

The general rules are:

  • A Distributor can be any version as long as it is greater than or equal to the Publisher version (in many cases the Distributor is the same instance as the Publisher).
  • A Publisher can be any version as long as it less than or equal to the Distributor version.
  • Subscriber version depends on the type of publication:
    • A Subscriber to a transactional publication can be any version within two versions of the Publisher version. For example: a SQL Server 2012 (11.x) Publisher can have SQL Server 2014 (12.x) and SQL Server 2016 (13.x) Subscribers; and a SQL Server 2016 (13.x) Publisher can have SQL Server 2014 (12.x) and SQL Server 2012 (11.x) Subscribers.
    • A Subscriber to a merge publication can be all versions equal to or lower than the Publisher version which are supported as per the versions life cycle support cycle.

Replication Matrix

[!INCLUDErepl matrix]

Additional Resources

Deprecated Features in SQL Server Replication
Replication features that have been retained in [!INCLUDEmsCoName] [!INCLUDEssCurrent] for backward compatibility, but, which will be removed in a future version of [!INCLUDEssNoVersion].

Breaking Changes in SQL Server Replication
Replication feature changes that might require changes to applications.

Upgrade Replicated Databases
Steps and considerations when upgrading SQL Servers participating in a replication topology.