MSDE Replication ?

I am designing a web site which will use MSDE at the back end (on a remote hosting provider). Uers will be able to edit small amounts of data (in limited no. of tables) in the web application, whilst I will need to 'upload' much larger amounts (and differ
ent tables) on a daily basis.
My question is how to design the replication ?
a) Merge replicate the whole Db ? or ...
a) Split the database into two databases (one being the stuff that users/browsers can edit) and one being the other stuff that will be 'uploaded' and use different replication techniques for each ?
c) Any other way ?
Also, are there any limitations on replication with MSDE ?
Many Thanks
Also, is it possible to use the Enterprise Manager in the Developer Edition to manage the replication or is this in breach of the licensing ?
|||Sarah,
this article explains MSDE limitations/restrictions for use in replication,
and the licensing implications:
http://support.microsoft.com/default...;en-us;Q324992
HTH,
Paul Ibison
|||Sarah,
I'm not sure about the topology. Presumably the website uses MSDE and you
need to replicate to a separate site (lets say B)? When you say 'upload' is
this a flow of data from the website to site B or vice versa? Is there any
posibility of data both at site B and the website being changed before
synchronization? When you 'upload' the data, is this the entire table(s) or
incremental changes?
Regards,
Paul Ibison
|||Hiya Paul,
Thanks for the link.
Re the topology ...
Website is running MSDE (say A) whilst I have a (home) server which can run MSDE or Developer Edition (say B).
Small amount of data/tables (say Tables-X) are updated by web users on A.
All data/tables are updated daily by me on B (this is the 'upload' TO the website).
It is possible that data in Tables-X will have been updated at both A and B and hence will need merging.
The other data changes (excepting Tables-X) will largely be updates to column values but also added rows (particularly early on in the sites lifetime).
I'm assuming I'll do a merge replication with B being the Publisher/Distributor and A being the Subscriber. (Or can I do a Merge Replication on Tables-X and Transactional replication on everything else ?)
|||Sarah,
I agree - merge for Tables-X. You'll need to consider conflict resolution,
or partition the data according to the subscriber eg use identity ranges, so
no conflicts will arise. If the other tables are only changed in one
direction then transactional would be definitely suitable there.
HTH,
Paul Ibison
|||Brilliant! Thanks Paul! That's reassuring
... but can I use the Development Edition of Enterprise Manager to handle or will this breach the licencing ?
|||This is one for MS licensing (a phone call). For what it's worth, my guess is that it is allowed, as I know of someone who uses the evaluation edition of SQL Server for the same purposes and insists it is legal.
HTH,
Paul Ibison
|||Many Thanks for your help Paul
sql