Skip to content

Latest commit

 

History

History
67 lines (47 loc) · 3.66 KB

File metadata and controls

67 lines (47 loc) · 3.66 KB
title Tutorial: Replicating Data Between Continuously Connected Servers | Microsoft Docs
ms.custom
ms.date 03/14/2017
ms.prod sql-server-2016
ms.reviewer
ms.suite
ms.technology
replication
ms.tgt_pltfrm
ms.topic article
applies_to
SQL Server 2016
helpviewer_keywords
tutorials [SQL Server replication]
replication [SQL Server], tutorials
wizards [SQL Server replication]
ms.assetid 7b18a04a-2c3d-4efe-a0bc-c3f92be72fd0
caps.latest.revision 21
author BYHAM
ms.author rickbyh
manager jhubbard

Tutorial: Replicating Data Between Continuously Connected Servers

Replication is a good solution to the problem of moving data between continuously connected servers. Using replication's wizards, you can easily configure and administer a replication topology. This tutorial shows you how to configure a replication topology for continuously connected servers.

What You Will Learn

This tutorial will show you how to publish data from one database to another using transactional replication. The first lesson shows how to use [!INCLUDEssManStudioFull] to create a publication. Later lessons show how to create and validate a subscription and how to measure latency.

Requirements

This tutorial is intended for users who are familiar with basic database operations, but who have limited experience with replication. This tutorial requires that you have completed the previous tutorial, Preparing the Server for Replication.

To use this tutorial, your system must have the following components:

  • At the Publisher server (source):

    • Any edition of [!INCLUDEssNoVersion], except Express ([!INCLUDEssExpress]) or [!INCLUDEssEW]. These editions cannot be replication Publishers.

    • [!INCLUDEssSampleDBUserInputNonLocal] sample database. To enhance security, the sample databases are not installed by default.

  • Subscriber server (destination):

    • Any edition of [!INCLUDEssNoVersion], except [!INCLUDEssEW]. [!INCLUDEssEW] cannot be a Subscriber in transactional replication.

    [!NOTE]
    Replication is not installed on [!INCLUDEssExpress] by default.

Note

In [!INCLUDEssManStudioFull], you must connect to the Publisher and Subscriber using a login that is a member of the sysadmin fixed server role.

Estimated time to complete this tutorial: 30 minutes.

Lessons in This Tutorial

Start the Tutorial

See Also

Replication Programming Concepts