Post reply

transaction replication replicates only one way???

  • January 24, 2005 at 6:41 am

    #162275

    Hello everyone

    I have set-up SQL Server 2000 transaction replication, but its only working

    one way? Data entered at the subscriber database is not making its way to

    the publishing database?

    I have Defined the distributor, Defined the publisher, defined a

    publication, created a push subscription and created a pull subscription.

    I am operating out of a test bed, I am only using one server to host the

    publisher, subscription and distribution database. The publication consists

    of just one table.

    Any ideas where I might be going wrong?

    Thanks in advance

    Russell J Morgan

  • January 24, 2005 at 7:44 am

    #538730

    If you actually want the data to be updateable on the publisher and subscriber you'll need to change to Merge replication rather than Transactional.


    Shamless self promotion - read my blog http://sirsql.net

  • January 24, 2005 at 9:10 am

    #538772

    Actually, along with Merge Replication (which is more compliated because it requires conflict resolution rules to be established), there are special options called "Immediate Updating" and "Queued Updating" which allow data to be changed at the subscribers.

    Think these special options can be used with Transactional and/or Snapshot replication, if memory serves.  But see SQL Books Online for the real story...

    - john

     

     

     

  • January 25, 2005 at 7:20 am

    #538939

    Look for Bi-directional replication on BOL or SQL Server Magazine.

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

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