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 - 2005-10-04 : 08:04:42
|
| Neal writes "We are not familiar with SQL replication tools and would appreciate any helpful assistance.We are currently looking at transferring data between 2 SQL servers (2003), with users amending records from 3 domains.Due to industry regulations, data is required to be up-to-date and accessable on each server. Therefore, we believe that 'Merge Replication' will be the most suitable method of data transfer for our business requirements.MY QUESTION IS THIS:After setting up a Publication between 2 servers, we set up a 'test' situation, whereby:User 1 amends an 'Age' field on a specified record on a table held on Server A database User 2 updates a 'Year' field ON THE SAME SPECIFIED RECORD AS ABOVE on the identical/replication table on Server B. BOTH AMENDMENTS WERE CARRIED OUT WHILST BOTH USERS WERE IN THE SAME RECORD.Similar 'tests' were carried out on several occasions and always resulted in only one of the updates being sucessful, as displayed on the Publisher Conflict Viewer (Publisher default).Can we record lock this data 'Pessimistically' from the server database level OR can data locking only be acheived via the accessing platform(?) (i.e. DAO MS Access)?The reason being that our SQL tables can be accessed via a variety of sources including MS Access/Internal Web Pages and in some cases by manual entry.We would want to reflect all changes on the record. Therefore we have to determine a secure method of capturing every change carried out on the record. There maybe occasions when the record is accessed by more than one user at a time, so how do we either prevent 2 or more people making changes to the record at the same time or can both changes be merged?Regards,Neal" |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2005-10-04 : 22:58:12
|
| i haven't personally done merge replication but it seems to me that the transactions are "bias", preferring one server over the other?are you using a separate distribution database to handle the conflict?--------------------keeping it simple... |
 |
|
|
|
|
|
Record locking with data replication.