| Reg Domaratzki \(iAnywhere Solutions\) 2005-03-30, 9:42 am |
| > The second possibility is to dynamically change what target is seen as
> the consolidated database (parent) by a particular remote database
> (child). This topic has been discussed from time to time in the
> newsgroups. I haven't tried it, and I don't have specific knowledge of
> anyone who has.
In theory, this could work. In practice, I think it would be a support
nightmare. As Breck pointed out, MobiLink is meant for hierarchical
synchronizations, not peer-to-peer. Although something as described above
could be set up, you're trying to put a round peg into a square hole,
although it will fit in this case.
Breck's two other suggestions are much more manageable IMHO.
--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup
iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set "Platform Preview" and "Time Frame" to ALL
"Breck Carter [TeamSybase]" < NOSPAM__bcarter@risi
ngroad.com> wrote in
message news:duko119ja2rb264
9l47n44avjtdfvgr4f1@
4ax.com...
> MobiLink supports hierarchical synchronization, not peer-to-peer.
>
> Having said that, three possibilities come to mind. First, design a
> multi-level hierarchy: B always synchronizes with HQ, and A and C
> always synchronize with B. That means if A, B and C are within range
> of one another, they can pass data via B. However, the only way for A
> and C to exchange data with HQ is via B. Three-level hierarchies are
> well understood in the world of MobiLink implementations.
>
> The second possibility is to dynamically change what target is seen as
> the consolidated database (parent) by a particular remote database
> (child). This topic has been discussed from time to time in the
> newsgroups. I haven't tried it, and I don't have specific knowledge of
> anyone who has.
>
> A third possibility exists if the there are disjoint sets of data
> being exchanged; one set of tables is exchanged with HQ, and a
> *different* set of tables is exchanged among A, B and C. Two
> different, independent MobiLink parent/child hiearchies could be set
> up. This would be a lot simpler (and safer?) than the second
> possibility, but I haven't tried it either.
>
> Understand that design, programming and administration complexity
> takes a *quantum* leap when you move to multiple levels/hierarchies.
>
> Breck
>
>
> On 22 Feb 2005 13:45:51 -0800, Aaron Neil wrote:
>
>
> --
> 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
|