SQLCe Replication best practice?

  • Thread starter Thread starter Earl
  • Start date Start date
E

Earl

I have an app where replication works fine (finally!). However, I'm curious
about how others handle their onboard database. Right now, my model is to:

1. Drop the onboard database before download synch and re-create with new
subscription
2. Drop the onboard database after upload synch.
3. Allow the user to login to an onboard database if one has not been
synchronized.

Any better suggestions?
 
Earl,

Why do you feel like you have to drop the database between synch events?
I can see deploying your app initially without the SQL CE db and upon first
execution letting merge replication create that first subscription, but
you're
incurring a lot of time to keep dropping and recreating the db (as well, the
list of unique subscriptions the server has to track are growing if you use
a different name each time).
--
Darren Shaffer
..NET Compact Framework MVP
Principal Architect
Connected Innovation
www.connectedinnovation.com
 
Thanks for replying Darren -- doesn't seem like many developers have any
insight into replication issues.

The reason I've been dropping the SQLCE db is because I had a lot of issues
in testing with simply merging the changes back and forth. Dropping and
recreating has worked well. I would certainly like to just maintain and
update the merge changes, so if you have any insight into what I should be
doing that is not published, I'd love to hear it.
 
Earl,

Can you highlight what is the problem you are facing that is forcing you to
drop and recreate the database? We are using merge replication in our
application for about 2-3 years with about 1000s of installations, without
any problem.

Vishal
 
Back
Top