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

Two way synchronization conflicts

forums › forums › SQLyog › Sync tools, Migration, Scheduled Backup and Notifications › Two way synchronization conflicts

  • This topic is empty.
Viewing 3 reply threads
  • Author
    Posts
    • July 5, 2004 at 1:59 pm #16056
      Shadow
      Member

      Currently you cannot do that with sja, but it's a good suggestion. Hope, it makes MAX!

      Unfortunately, I can't even think of a workaround using sja, unless the target and source dbs are updated in blocks (e.g.: s. db is updated p.m., while target is updated in the afternoons). In this case WHERE clauses can be used to select which rows to compare!

    • July 5, 2004 at 5:18 pm #16057
      Ritesh
      Member

      One workaround could be to determine the “source” and “target” using a separate query, generate the SJA XML file dynamically to swap the “source” and “target” (if required) and then run SJA.

      However, this wont give you a row level swapping option.

    • July 12, 2004 at 3:19 am #16058
      mwbourgeois
      Member

      Sorry I forgot to check this post for so long.

      The reason I can't dynamically choose source and target is because which database is correct cannot be predicted on the whole table level. Some rows from one db server will be correct, and some from the other. I could write a script to do the synchronization by joining the tables, but that's no easy task if the tables are on seperate servers.

    • July 13, 2004 at 3:13 pm #16059
      Shadow
      Member

      Well, in this case you'll have to write a separate app to do the sync for you. It would not be a bad idea though to have a sync option that determines one or more columns and conditions that would drive the two-way sync process!

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