Unsupported Screen Size: The viewport size is too small for the theme to render properly.

2 way SJA does not update on target SQL server

forums › forums › SQLyog › Sync tools, Migration, Scheduled Backup and Notifications › 2 way SJA does not update on target SQL server

  • This topic is empty.
Viewing 2 reply threads
  • Author
    Posts
    • December 23, 2004 at 4:54 pm #8717
      ferretrex
      Member

      I tried to use a two way SJA to make changes on target. I scheduled it every 5 minutes. For some reason, when I go to the remote sql server and make changes. Do not touch the master database. It appears that all those changes were over written. It will only add new records in the target area. Maybe there is a conflict with the master and remote area. How do I avoid conflicts so that if I make updates on the target area it will update on the master area. At this time all updates changes on the target database are replaced with the master information. It seems that it is always conflicting. Is there a way I can have this software compare by timestamp or something? A friend recommended triggers but am not sure if mysql accepts triggers. And, am not sure if the SJA will recongnize the triggers.

      Hope someone can help!

      Thank you,

      Dean

    • January 21, 2005 at 4:44 pm #16748
      pektop
      Member

      have same problem. two way sync workin as a one way. Any help please?

    • January 22, 2005 at 1:33 am #16749
      peterlaursen
      Participant

      If the value of the Primary Key is identical for some rows in the two databases, SJA will ALLWAYS overwrite the target with data from the source. That's how it's supposed to work! Are you sure that's not the problem ?

      SJA identifies the rows by PK and nothing else. It's been requested from time to time by users that there should be other options, and Ritesh has (a I remember) written here that they will look into that, but I'm not sure if there is any conclusion yet.

      However I believe, that it should be possible to use any unique index. A timestamp could be part of such a unique (composite) index. Problem with timestamps however is that the format has changed from different Mysqlversions. So if not the server versions are identical, results could be unpredictable.

  • Author
    Posts
Viewing 2 reply threads
  • You must be logged in to reply to this topic.