[Ritesh]

I think its a problem with the new client library. I will double check it and let you know.

[Ritesh]

We are working on the SSL problem and I will reply back soon.

[Ritesh]

JasonPotter wrote on Jun 2 2004, 04:43 PM:

Hi Guys,

just saw another post that stated sja can handle multiple keys.  Now just have to confirm it can handle a column being auto inc at one end and not at the other.

Cheers

Jason

STRUCTURE and PRIMARY KEY has to be exactly same on both the source and target server.

SJA correctly handles multiple keys provided that the order of the columns in the keys are the same.

[Ritesh]

JasonPotter wrote on Jun 2 2004, 12:13 PM:

Thanks for the response.

Though I thought sja will delete the enteries in the target if they are not in the source or is this a configurable feature? Hence when you do the first sync the target will become exactly like Source1 and then after the second sync the target will exactly be like Source2, hence wiping out the data entered into the target from the first sync.

Also what would the issues be if any, if Source1 and Source2 tried to do their syncs at the same time. In my case Source1 and Source2 are not always connected to the net and initiate their on connections. I would prefer not to have to specify connect times as these Source db's will connect to the net via GPRS and I am not always going to have a signal. So if I have a signal and can make a net connection via gprs I want to do the sync straight away. So there is a chance of 2 sync's running at the same time.

I look forward to your response on both points.

Cheers

Jason

By default SJA will delete the extra rows that are present in target but not in source. Starting from SQLyog 3.7, you can configure the synchronization agent for not to delete extra rows in the target.

[Ritesh]

SJA is a perfect solution for you. You need to run two sync sessions.

1st session:Make source1 the source and master the target.

2nd session:Make source2 the source and master the target.

Do send me your comments on the result.

[Ritesh]

This feature will be added in one of our next releases.

Till then you can execute ALTER TABLE statement to set the character-set to utf8.

[Ritesh]

The link is http://www.webyog.com/sqlyog/SQLyog364.exe and not http://www.webyog.com/sqlyog/SQLyog364.com

Please download the binary and do tell me the result.

[Ritesh]

SQLyog uses PRIMARY KEY as the locus for determining changes in the data. If you need to merge data from two sources then you need to have unique primary key values across the databases.

[Ritesh]

Sorry but SJA can only be used to sync data between two MySQL databases.

[Ritesh]

robmann wrote on May 28 2004, 03:21 PM:

So can you sync the online data and the local data even though you are entering new data all the time both online and locally? I read something about if primary keys are the same the target gets overwritten? is there a way to sync if you have the same primary keys in each table?

Yes 🙂 SJA is perfect for such situation.

You require 2-way sync between the source and the target database. The only thing you need to keep in mind is that SJA will try to bring the target in sync with the source. In case of conflicting Primary Keys, the data from the source overwrites the target data.

e.g. if you have the following condition:

source:

=========

1 SQLyog

2 Ritesh

target:

========

1 SQLyog Agent

3 MySQL

After you run the sync the source and target will become:

source:

==========

1 SQLyog

2 Ritesh

3 MySQL

target:

==========

1 SQLyog

2 Ritesh

3 MySQL

Note: The above is only applicable if you perform 2-way sync.

HTH

[Ritesh]

I believe you are using SJA for Linux. As I can see, you are doing a 2-way sync. SJA should work in this situation.

Can you send me a backup of the database so that I can run a sync at my place?

[Ritesh]

SQLyog is supposed to work properly with binary-data. Anyway, it will be nice if you can send me a backup of your database.

[Ritesh]

Thanks for your suggestion 🙂

I have forwarded your request to my development team.

[Ritesh]

Check the option:

“Set FOREIGN_KEY_CHECKS=0” in Export As Batch Script dialog.

[Ritesh]

We are looking your issue. Give us some time 🙂

[Author]

Posts