Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
DaveDunlap
Starting Member
1 Post |
Posted - 2005-11-25 : 17:26:09
|
We're writing a .NET custom application using VS 2005 - C# that will be running on MSSQL and MDSE. Central server will of course be on MSSQL 2005 and there will be remote users running (the way we see it) SQL 2005 Express Edition.We need to replicate data between the server and the remotes - Remotes may only get a filtered version of the dataset that's on the server. The datastucture is not trivial - perhaps 20 or 30 tables.The functionality of the app will be similar in many respects to a typical CRM system that has both network users and remote users who run disconnected and sync.Both remote and network users will be creating new records, editing information, etc.I've been reading through the SQL 2005 Books OnLine info about Replication in an effort to get a handle on how best to set up Replication.My impression is that we should use column level Merge Replication and that we will need to write some custom "business logic" code to handle conflict resolution. Since the network users function mostly to support the efforts of the remote users and the remote users will definitely be editing records entered by themselves and others, we will need to really have the replication and conflict resolution situation "dialed in".Remote users will need to sync (replicate) on demand and most of the time they will be doing it over the internet, not when connected on the LAN.We figure that the "average installation" for our application will have 5 or so network users and probably about that same number of remote users.I am somewhat SQL literate but have never set up or used SQL Replication so any and all suggestions, hints, thoughts and gotchas would be very much appreciated.Thanks!Dave DunlapMARKET/FX, Inc.Irvine, CAwww.marketfx.com |
|
|
|
|