Re: Merge replication or manual one?

From: Darren Shaffer (darrens_at_nospam.com)
Date: 10/08/04 

Date: Fri, 8 Oct 2004 08:18:15 -0600

The decision is less about capabilities than about the type of connectivity
and
administration you can tolerate. Merge, RDA, or a manual approach can all
do what you describe as requirements below.

If you're on a high speed network (802.11), Merge, RDA, or a web-services
based approach to replication are all great options. Moving to a WWAN
(GPRS)
scenario, I'd eliminate merge based on my experience trying it for all of
Frontier Airlines
baggage handlers and then having to switch to RDA due to the bandwidth
required
by merge. Merge is also more administratively intensive as you have to
monitor
the server for conflicts that could not be auto-resolved and for other
issues.

Beyond that, remember that RDA uses optimistic concurrency, so it is
possible
for changes from device B to overwrite changes from device A on the server.

I've started to use my own web-services based replication strategy for
almost
all of my projects. It works well outside the firewall and I have complete
control
over concurrency management for each entity I want to synchronize. One tip:
make everything you need to be unqiue across the system a GUID, it will save
you
headaches later.

Good luck with your project,

-Darren

"Freestyler" <freestyler@gazeta.pl> wrote in message
news:ck65ug$3l1$1@inews.gazeta.pl...
>I have a one SQL Server 2000 and plenty of SQL Servers CE on PocketPC's.
> My goal is to replicate the Server 2k changes into each SqlServerCE.
> There is other set of data to be send to each SQL Servers CE.
> For example stored procedures with parameter (POCKET_PC_ID) can give the
> valid data for each PocketPC.
> All of data produced on PocketPC shold be transformed into SQL Server
> 2000.
> Data from two PocketPC's should differ on the SQLServer2000 side ( for
> example Invoice 5 from PPC1 is not the Invoice 5 from PPC2 - )
> Is it all easy task for merged replication, or should I rather use manual
> one?
> Another question is what common replication problems cannot be solved by
> merged replication?
>
> Thanks for any ideas,
> Regards
> Freestyler
>

Relevant Pages

  • Re: Problem in the rda.Push operation
    ... I would not suggest using IDENTITY columns with RDA. ... The error message you are receiving sounds more like a Merge replication ... For some reason, SQL Server ...
    (microsoft.public.sqlserver.ce)
  • Re: How to synchronize SQL CE 2005 with SQL Express or Standard 20
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... server 2005 to try out merge replication. ... We intend to buy the Standard edition for our own purposes ... both RDA and merge replication rely on IIS to ...
    (microsoft.public.sqlserver.ce)
  • Re: How to synchronize SQL CE 2005 with SQL Express or Standard 20
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... server 2005 to try out merge replication. ... We intend to buy the Standard edition for our own ... both RDA and merge replication rely on IIS ...
    (microsoft.public.sqlserver.ce)
  • Re: How to synchronize SQL CE 2005 with SQL Express or Standard 20
    ... One other solution would be to write your own home grown replication web ... both RDA and merge replication rely on IIS to ... RDA works with all versions of SQL Server. ... replication to sync multiple mobile devices since both merge and RDA use IIS ...
    (microsoft.public.sqlserver.ce)
  • Re: Transactional replication from SQL Server 2005 to SQL Server 7 - how?
    ... SQL Server 7.0 from the SQL2005 management tools but I would encourage to ... primary keys are replicated as unique indexes if you ... configure replication using the SQL2000 Enterprise Manager. ... If you plan to reinitialize your SQL2000->SQL2005 subscription in the ...
    (microsoft.public.sqlserver.replication)
Loading