|
Home > Archive > SQL Anywhere Mobile > May 2005 > Beginners question
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Beginners question
|
|
| Mad Vlad 2005-05-18, 7:24 am |
| We have a Powerbuilder 7.0.3 database running on SQL Anywhere 9.
We're looking into using SQL Remote/Mobilink for remote access from UK to
Switzerland.
We have never researched database replication before, and I understand that
SQL Remote/Mobilink use data synchornization to execute transaction log
between the sites on regular time intervals. We are concerned with primary
key conflicts.
Basically, our application uses its own procedures to generate unique
references which are used as primary keys in a number of tables. We do not
know how Mobilink takes care of potential primary key conflicts, so is it
likely that we will have to change our application and/or database primary
key structure to achieve database replication?
Thanx
| |
| Breck Carter [TeamSybase] 2005-05-18, 7:24 am |
| MobiLink uploads from multiple remote databases to one consolidated
database must not insert two rows with the same primary key; that
causes a fatal error. MobiLink does not handle this situation, it's up
to your design to ensure that the same primary key value is not
inserted on two or more remotes. You can use a number of approaches;
IMO the DEFAULT GLOBAL AUTOINCREMENT and GLOBAL_DATABASE_ID approach
is best.
Breck
On 18 May 2005 03:25:36 -0700, "Mad Vlad" <vlad@NOSPAMpcr.ltd.uk>
wrote:
>We have a Powerbuilder 7.0.3 database running on SQL Anywhere 9.
>
>We're looking into using SQL Remote/Mobilink for remote access from UK to
>Switzerland.
>
>We have never researched database replication before, and I understand that
>SQL Remote/Mobilink use data synchornization to execute transaction log
>between the sites on regular time intervals. We are concerned with primary
>key conflicts.
>
>Basically, our application uses its own procedures to generate unique
>references which are used as primary keys in a number of tables. We do not
>know how Mobilink takes care of potential primary key conflicts, so is it
>likely that we will have to change our application and/or database primary
>key structure to achieve database replication?
>
>Thanx
>
--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com
| |
| Shuchit 2005-05-19, 7:24 am |
| =
>
> Basically, our application uses its own procedures to generate unique
> references which are used as primary keys in a number of tables. We do not
> know how Mobilink takes care of potential primary key conflicts, so is it
> likely that we will have to change our application and/or database primary
> key structure to achieve database replication?
See <http://tinyurl.com/988vg> which points to
<http://www.ianywhere.com/developer/...e/0902/en/html/
dbmlen9/00000049.htm>
Shuchit
|
|
|
|
|