Scheduled Syncs

[infringer]

This is not a huge problem… just reporting it.

I have a scheduled sync, that ran last night and reported this.

Sync started at: Wed Sep 15 18:00:02 2010

Table SrcRows TgtRows Inserted Updated Deleted

========================= ======= ======= ======== ======= =======

`asstdata` 1690 0 2 0 0

`busdata_2010` 4246 0 240 0 0

`busdata_2011` 784 0 9 0 0

`busmstr_2010` 3201 0 676 0 0

`busmstr_2011` 446 0 446 0 0

`drvrdata` 272 272 0 0 0

`employee_2010` 474 0 128 0 0

`no2work` 6197 0 42 0 0

PRIMARY KEY mismatch for '`timelines_2010`' table

PRIMARY KEY mismatch for '`timelines_2011`' table

Sync was unsuccessful.

I know what the problem is, but it is not a PRIMARY KEY. I added 2 indexes to these two tables yesterday, and forgot to fix the target server as well.

Just might confuse someone. When I first saw it I was startled, and looked at the primary key and it was exactly the same as always. Then I remembered the indexes.

-David

[peterlaursen]

This has already been fixed and the fix will be available from next release.  Actually before Indexes needed to be the same.  But the error message was misleading (and there even were some situations where they needed not be quite the same).

Actually we a SJA for Linux ready with this fix.  Another user confirmed the fix using this one.  If it is priority for you I think we can build SJA for Windows as well tomorrow.

EDIT&ADD: From next release tables may have different indexes with the exception of the Primary Key (or Unique Index) used for sync.

[Khushboo]

Hi David,

We have released 8.62 GA with this fix.

“Data Sync will now ignore differences as regards indexes on source and target tables except for the Primary Key/Unique Index used for sync. There is no need to require that all indexes are the same.”

Please refer to:

http://www.webyog.com/blog/2010/10/08/sqlyog-mysql-gui-8-62-released/

Thanks & Regards,

Khushboo

[Author]

Posts