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. Replication In SQL Server 2005?

Replication In SQL Server 2005?

Scheduled Pinned Locked Moved Database
databasesql-serversysadminhelpquestion
6 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.
  • C Offline
    C Offline
    cocoonwls
    wrote on last edited by
    #1

    Hi all, I am facing a problem on whether using Transactional replication or Merge replication technique in SQL Server 2005. In my senario, i have 2 database which located in one sql server,named D1 and D2. Now, i would like to sync some of the table between these 2 database, and the data will frequently update/delete/insert by user into D1 or D2 and user should have the latest data for proceed operation. So, may i know which technique should be use in this senario? Any suggestion or tips are welcome. Note: And what if the 2 database are located in different server(different location)? thanks in advance cocoonwls

    H 1 Reply Last reply
    0
    • C cocoonwls

      Hi all, I am facing a problem on whether using Transactional replication or Merge replication technique in SQL Server 2005. In my senario, i have 2 database which located in one sql server,named D1 and D2. Now, i would like to sync some of the table between these 2 database, and the data will frequently update/delete/insert by user into D1 or D2 and user should have the latest data for proceed operation. So, may i know which technique should be use in this senario? Any suggestion or tips are welcome. Note: And what if the 2 database are located in different server(different location)? thanks in advance cocoonwls

      H Offline
      H Offline
      Hulicat
      wrote on last edited by
      #2

      I had the same scenario and ended up using transactional replication @ 2 hour intervals. I was going @ 15 minute intervals with no issues but I wanted to have some latency in the event the source DB has some problems it gives me time to shut down the replication. I didn’t use merge because if one DB gets hosed or corrupted they both get hosed. I hope that helps.

      Regards, Hulicat

      C 1 Reply Last reply
      0
      • H Hulicat

        I had the same scenario and ended up using transactional replication @ 2 hour intervals. I was going @ 15 minute intervals with no issues but I wanted to have some latency in the event the source DB has some problems it gives me time to shut down the replication. I didn’t use merge because if one DB gets hosed or corrupted they both get hosed. I hope that helps.

        Regards, Hulicat

        C Offline
        C Offline
        cocoonwls
        wrote on last edited by
        #3

        Hi Hulicat, Thanks for your helping hand. Is Transactional replication bidirectional? i need to do sync for both side, that mean either D1 or D2 update, then both of them are update. And the interval time is my piority concern, i have to do it as fast as possible to allow user to use the latest data, may be in 30sec or even per transaction. thankx in advance. regards cocoonwls

        H 1 Reply Last reply
        0
        • C cocoonwls

          Hi Hulicat, Thanks for your helping hand. Is Transactional replication bidirectional? i need to do sync for both side, that mean either D1 or D2 update, then both of them are update. And the interval time is my piority concern, i have to do it as fast as possible to allow user to use the latest data, may be in 30sec or even per transaction. thankx in advance. regards cocoonwls

          H Offline
          H Offline
          Hulicat
          wrote on last edited by
          #4

          You need to use "merge" if either database can be updated,

          Regards, Hulicat

          C 1 Reply Last reply
          0
          • H Hulicat

            You need to use "merge" if either database can be updated,

            Regards, Hulicat

            C Offline
            C Offline
            cocoonwls
            wrote on last edited by
            #5

            Hi Hulicat, Thanks for your information.I got it ;) .But then is there any solution/suggestion to prevent the problem you were mentioned in your first post? regards cocoonwls

            H 1 Reply Last reply
            0
            • C cocoonwls

              Hi Hulicat, Thanks for your information.I got it ;) .But then is there any solution/suggestion to prevent the problem you were mentioned in your first post? regards cocoonwls

              H Offline
              H Offline
              Hulicat
              wrote on last edited by
              #6

              Not to my knowledge; it's one of the caveats of using "merge" replication.

              Regards, Hulicat

              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