Subject | Creation of a "Replication Friendly" database. Any rules of thumb? |
---|---|
Author | acegracely |
Post date | 2005-03-23T16:30:23Z |
Hi,
I need to make my database replication friendly. (don't worry, it is
not in use yet. I have just converted over from Advantage Database
Server).
Am I right in thinking that the easiest way is to make all primary
keys an integer with a generator?
If so, will this fall over if replication is bi directional i.e.
depending on the time interval between replications, both ends could
add a number of records thus the generators could be out of sync.
Also, how does this affect foreign key constraints IOW can I create a
foreign key constraint on a unique index rather than the primary key
field?
Is there any firebird documentation to help with this?
I need to make my database replication friendly. (don't worry, it is
not in use yet. I have just converted over from Advantage Database
Server).
Am I right in thinking that the easiest way is to make all primary
keys an integer with a generator?
If so, will this fall over if replication is bi directional i.e.
depending on the time interval between replications, both ends could
add a number of records thus the generators could be out of sync.
Also, how does this affect foreign key constraints IOW can I create a
foreign key constraint on a unique index rather than the primary key
field?
Is there any firebird documentation to help with this?