MSDE 2K Merge replication without network

I'm new to replication, but have a challenging requirement...
I have multiple MSDE 2K instances that will be used by a surveying crew that
may be distributed across many miles - sometimes in jungle or desert
environments where they never even see each other.
All/any data in any instance is updateable; all changes must be propagated -
at irregular intervals (daily or?) to all other instances. There is no
designated "master" (or perhaps all instances could be considered "masters").
We can live with a hub-and-spoke replication topology (ie, all replication
occurs via a hub instance at the field camp, which then, eventually,
replicates to all the other spokes).
===> The instances are NOT (and are NEVER) connected over a network! (not
even wireless - although we should be able to at least keep the system clocks
synchronized, if that's required for reliable synchronization, by having
each system have a GPS receiver).
Therefore, all synchronization must be via files (flash drive, etc). Even
the definition/setup of the synchronization (subscriptions) must not require
a network connection.
Can Merge replication be implemented between MSDE instances, given these
network constraints?
Thanks!
David
Unless you provide at least an occasional network connectivity between
publisher and subscribers merge replication cannot be implemented.
Yury
"David" <David@.discussions.microsoft.com> wrote in message
news:32C0446B-5D11-4FAF-AB03-70F4096642BC@.microsoft.com...
> I'm new to replication, but have a challenging requirement...
> I have multiple MSDE 2K instances that will be used by a surveying crew
> that
> may be distributed across many miles - sometimes in jungle or desert
> environments where they never even see each other.
> All/any data in any instance is updateable; all changes must be
> propagated -
> at irregular intervals (daily or?) to all other instances. There is no
> designated "master" (or perhaps all instances could be considered
> "masters").
>
> We can live with a hub-and-spoke replication topology (ie, all replication
> occurs via a hub instance at the field camp, which then, eventually,
> replicates to all the other spokes).
> ===> The instances are NOT (and are NEVER) connected over a network! (not
> even wireless - although we should be able to at least keep the system
> clocks
> synchronized, if that's required for reliable synchronization, by having
> each system have a GPS receiver).
> Therefore, all synchronization must be via files (flash drive, etc). Even
> the definition/setup of the synchronization (subscriptions) must not
> require
> a network connection.
> Can Merge replication be implemented between MSDE instances, given these
> network constraints?
> Thanks!
> David
|||its probably better to use transactional replication with a local dummy
subscriber. Collect the contents of msrepl_commands and then mail them back
and forth. This will be a list of all database activity which you can run on
each node for synchronization purposes.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"David" <David@.discussions.microsoft.com> wrote in message
news:32C0446B-5D11-4FAF-AB03-70F4096642BC@.microsoft.com...
> I'm new to replication, but have a challenging requirement...
> I have multiple MSDE 2K instances that will be used by a surveying crew
that
> may be distributed across many miles - sometimes in jungle or desert
> environments where they never even see each other.
> All/any data in any instance is updateable; all changes must be
propagated -
> at irregular intervals (daily or?) to all other instances. There is no
> designated "master" (or perhaps all instances could be considered
"masters").
>
> We can live with a hub-and-spoke replication topology (ie, all replication
> occurs via a hub instance at the field camp, which then, eventually,
> replicates to all the other spokes).
> ===> The instances are NOT (and are NEVER) connected over a network! (not
> even wireless - although we should be able to at least keep the system
clocks
> synchronized, if that's required for reliable synchronization, by having
> each system have a GPS receiver).
> Therefore, all synchronization must be via files (flash drive, etc). Even
> the definition/setup of the synchronization (subscriptions) must not
require
> a network connection.
> Can Merge replication be implemented between MSDE instances, given these
> network constraints?
> Thanks!
> David