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 |
|
GilDanziger
Starting Member
2 Posts |
 Posted - 2005-07-05 : 14:28:06
|
| Hi,I understood that the implementation of offline clients (doesn't matter if it's PDA with SQL CE/Mobile or windows XP with MSDE/Express) and Merge replication in the SQL Server is good in theory but difficult to manage and requires a lot of extra handling issues like opening ports and adding users granted to run the processes for the replication process.Is it true? Are there any improvements in 2005 in these issues (I know about the option to replicate through iis so the port problem is now solved?!).I'll be glad if anybody knows and can write about products in the open market which used this architecture.Thanks,Gil. |
|
|
KLang23
Posting Yak Master
115 Posts |
Posted - 2005-07-05 : 18:55:03
|
| It works, and it can work well.I designed and implemented the DB architecture to manage an automated prescription and patient scheduling system used by physicians walking around the office with PDAs (SQLCE) connected to a WAP connected to a local SQL instance. Formulary information was kept up-to-date, and prescriptions printed on demand.You may need to write a custom "synchronization" routine to force a snapshot application on demand, sync on-demand, and use SQL's alerting features to stay on top of problems, but overall, merge replication works, and if the db design is good, it works well.As with anything worthwhile, it takes some effort to establish a solid infrastructure, security scheme, etc., but that is part of the game anyway.Good luck with this! I can be a lot of fun. |
 |
|
|
|
|
|
|
|
Administrating Merge replication in 'SQL Server'