Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Database & SysAdmin
  3. Database
  4. SQL server 2008 Replication problem

SQL server 2008 Replication problem

Scheduled Pinned Locked Moved Database
databasecsharpsql-serversysadminhelp
4 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • H Offline
    H Offline
    Hy Chanhan
    wrote on last edited by
    #1

    Dear experts, I need your helps now. I setup merge replication from Server A to server B and Server C and then i want to do the transaction replication from server A to another server D but i got a problem: --------

    Publication cannot be subscribed to by Subscriber database because it contains one or more articles that have been subscribed to by the same Subscriber database at merge level.
    Changed database context to (.Net SqlClient Data Provider)

    ------------- how to resolve it? Thanks for your helps.

    _ 1 Reply Last reply
    0
    • H Hy Chanhan

      Dear experts, I need your helps now. I setup merge replication from Server A to server B and Server C and then i want to do the transaction replication from server A to another server D but i got a problem: --------

      Publication cannot be subscribed to by Subscriber database because it contains one or more articles that have been subscribed to by the same Subscriber database at merge level.
      Changed database context to (.Net SqlClient Data Provider)

      ------------- how to resolve it? Thanks for your helps.

      _ Offline
      _ Offline
      _Amy
      wrote on last edited by
      #2

      Hi, Take a look at these links: http://www.techrepublic.com/blog/howdoi/how-do-i-configure-transactional-replication-between-two-sql-server-2005-systems/123[^] http://msdn.microsoft.com/en-us/library/ms152536%28v=sql.105%29.aspx[^] Here[^] is a video to Setup Transactional Replication.

      Read the article "Table Valued Parameters". Cheers --Amit

      H 1 Reply Last reply
      0
      • _ _Amy

        Hi, Take a look at these links: http://www.techrepublic.com/blog/howdoi/how-do-i-configure-transactional-replication-between-two-sql-server-2005-systems/123[^] http://msdn.microsoft.com/en-us/library/ms152536%28v=sql.105%29.aspx[^] Here[^] is a video to Setup Transactional Replication.

        Read the article "Table Valued Parameters". Cheers --Amit

        H Offline
        H Offline
        Hy Chanhan
        wrote on last edited by
        #3

        Hi, If I setup only transaction replication it is working fine but when i setup Merge replication in Server A and after that i setup one more Transaction replication then i gave me the errors as mentioned. Actually i have one server A do merge replication to clients. And now i want to do one more transaction replication in Server A to others but it occurred errors. can we do Merge replication and transaction replication in the server A? ---

        _ 1 Reply Last reply
        0
        • H Hy Chanhan

          Hi, If I setup only transaction replication it is working fine but when i setup Merge replication in Server A and after that i setup one more Transaction replication then i gave me the errors as mentioned. Actually i have one server A do merge replication to clients. And now i want to do one more transaction replication in Server A to others but it occurred errors. can we do Merge replication and transaction replication in the server A? ---

          _ Offline
          _ Offline
          _Amy
          wrote on last edited by
          #4

          Basically with merge replication when a synchronization occurs, the final state of the rows is what is merged with the other side. So if I have a stock tracking table which each stock is updated thousands of times between synchronizations only the last value of the stock will be replicated. With transactional replication with updateable subscribers the changes (the DML) will be replicated as transactions. So if a row in our stock table is updated 1,000 times there will be 1000 indivdual transactions will be replicated. Now updateable subscribers is being deprecated and will likely not show up in SQL 11 and peer to peer is the desired upgrade path. So if you need transactions replicated transactionally you would want updateable subscribers, if you want bi-directional synschronization between nodes which are frequently disconnected - merge replication is the way to go.

          Read the article "Table Valued Parameters". --Amit

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups