SJA DB Structure Recomendations

[jdhr]

Hi,

I was wondering if sja has recomendations in the process of creating a database… related to the syncronization….

¿Does it have a better performance with InnoDB type tables? or ¿Does it support the FKeys? or

¿Does it ensurance its sync. if u organize your PKeys in the header of the tables in your DB? or something like that….

Thanks for your answer.

[Shadow]

Sja has only one requirement: primary key must be defined for all tables that you want to sync. The speed of the sync is influenced by the structure of tables, but there is no sja specific recommendation as sja uses standard SQL commands to retrieve and manipulate data.

Therefore in case of InnoDB tables sja honors the foreign key restrictions (in fact, it is not sja, the InnoDB table handler does the job), but sja can be instructed to turn FK checks off while syncing. This is highly recommended as it is difficult to force sja to sync tables in a particular order.

[jdhr]

Thanks for your answer Shadow,

about primary keys, does sja have any problem if I define mor than one Primary Key on a Table??

[Ritesh]

jdhr wrote on Jul 27 2004, 12:48 PM:

Thanks for your answer Shadow,

about primary keys, does sja have any problem if I define mor than one Primary Key on a Table??

No 😀 SJA will work perfectly even if you define more then one Primary Key on a Table.

[Shadow]

Quote:

about primary keys, does sja have any problem if I define mor than one Primary Key on a Table??

You cannot define more that one PK per table (error 1068), it is impossible to do so in all RDBMs, as a PK uniquely identifies a record. But a PK may have multiple fields, and sja will handle those PKs perfectly.

[Author]

Posts