Merge Replication with SQL Server 2005 (server to server)

Discussion in 'microsoft.public.sqlserver.replication' started by DL, Dec 19, 2008.

  1. DL

    DL Guest

    I've got merge replication between two servers (bi-diretional) data
    merge working. Now, when I attempted to do a bit more, got into a
    problem. Here's the scoop.

    Publisher and Distributor = Central Server which has the main database

    Scenario A
    * using Pull subscription
    * using a brand new DB
    subscribe to the merge publication only

    a) I've got the above configuration workiing (b-directional data
    update (insert, update and delete) the other day.
    b) Downside: to sync everything, tables, SPs, views, UDFs etc. is
    quite resources-intensive.

    Scenario B
    * using Pull subscription
    * using an identical database (to the publisher's db) with data
    subscribe to the merge publication only

    Well, be default, the subscriber will 'import' the snapshot (db schema
    etc.), however, it's not needed in this case. I don't see an option
    from the subscription to disable snapshot sync. There must be a way
    to do it. How?

    DL, Dec 19, 2008
    1. Advertisements

  2. Use a no-sync subscription.
    Hilary Cotter, Dec 22, 2008
    1. Advertisements

  3. DL

    DL Guest

    A quick search indicates that one can do that during the subscription
    creation process. Since I have one already, I looked at its
    properties, however, couldn't find anywhere that would allow me to set
    no-sync or am I missing something here? Or could we do it from
    scripting? Then which proc?

    DL, Dec 22, 2008
  4. DL

    Paul Ibison Guest

    Have a look here for more info: From BOL: "A
    subscription is a "no sync" subscription if a value of none is specified for
    the @sync_type parameter of sp_addmergesubscription or
    sp_addmergepullsubscription. This type of subscription is not recommended for
    merge replication.".
    Paul Ibison
    Paul Ibison, Dec 29, 2008
  5. DL

    DL Guest

    Thanks. Actually I'd like to step back for a sec, that is, I'll now
    do uni-directionary replication first. Then, topology-wise, it would
    be a) snapshot; b) transaction. Business case, DR, so, I intend to
    use server push to a subscriber like every 1 hour. Some pecularity
    here, we have desktop application running against the main/publisher
    server all the time and the app created voice data dynamically and
    save them to the DB. Yesterday I experienced error during data saving
    but it's sort of false positive, data were actaully saved. Without
    the replication coming into play this sort of error never occur, so,
    is it a bug from MS Replication technology side or on the incorrect
    usage side? Secondly, i was thinking to remove table/article that
    include the column of such voice data for the replication's
    transactional process then create a new replication or some other
    process just for this set of data. But this approach is kind of

    For another, has SQL Server 2008's replication technology improved in
    terms of ease of use and bugginess?
    DL, Dec 30, 2008
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.