Replication alternatives for SQL Server 2016 Web Edition

  • We have a SQL Server 2016 Web Edition instance that we ideally need to replicate a subset of data from. However, Web Edition only supports replication as a subscriber, not as a publisher. The cost of upgrading to Standard Edition does not make business sense, and so we are looking for a scalable alternative solution.

    Our predicament is very similar to that described in the following post, in terms of replicating and log shipping a subset of data out to another site:
    https://serverfault.com/questions/249046/log-shipping-on-select-tables

    The suggestion posed here is to use the Microsoft Sync Framework. However, we have not found much in the way of examples as to how to practically set this up from a SQL Server perspective and what the limitations are.

    Can anyone please guide us how to implement this, or point us in the direction of  an alternative to repllication which would work on Web Edition (as a publisher)? We'd like to avoid having to create a whole suite of additional "sync" tables in our production database if possible, as we are looking to replicate quite a few tables and want to keep the administrative effort to a minimum.

    Edition:
    Microsoft SQL Server 2016 (SP1) (KB3182545) - 13.0.4001.0 (X64) Oct 28 2016 18:17:30 Copyright (c) Microsoft Corporation Web Edition (64-bit) on Windows Server 2016 Standard 6.3 <X64> (Build 14393: ) (Hypervisor)

  • Web supports the Import and Export Wizard, I've not played with Web edition, but in the others you can save a wizard package as a job and run it when needed.  Unsure if that's an option in Web but would be one way to replicate tables.

  • Thank you, yes the Import and Export Wizard does appear to be an option in Web Edition. We will see if it could provide an alternative solution.

    Does anyone have any experience of this Microsoft Sync Framework? We've found several pages suggesting it but not much on how to actually implement it.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply