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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-09-23 : 08:03:08
|
| Paul writes "I am migrating a label printing application that was based on Oracle tables with Entera (out-of-business) Remote Procedure Calls from a VB client to SQL Server. I need to replicate changes to the SQL Server tables on to a heterogenious database (MS Access). I have simplified the data requirements as follows. Approximately 10 tables, most small. One table changes many times a day and averages 1000 rows, one changes several times a week and averages 10,000 rows. The rest may change monthly on average and contain at most a couple hundred rows. There are 15 clients around the country that need access to this data, but do to remoteness are not always connected. The remote sites do not need to update the data, they just need the latest version of the data.The three options I am considering are: 1. Merge Replication, pulling the data from the client (if possible). Can I prevent changes from going back to SQL Server? 2. Snapshot Replication, but concerned that pulling the 10,000 row table each time will be too time consuming. 3. Manually coding in the remote client (VB) to query the tables individually and pulling in the changes (probably a last modified column in each table, and not allowing deletes to rows).I have been reading books on line, your web site as well as Microsoft's and SSWUG's, but do to my newness to SQL Server I'm a little tentative as to which direction to choose.Thanks for any assistance.Paul Murray" |
|
|
|
|
|
Merge or Snapshot Replication or Not