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 |
|
Mike2265
Starting Member
6 Posts |
Posted - 2004-05-03 : 05:46:45
|
| Hello (Back on after a while and my old login seems to have dissapeared),We've set up merge replication between a main database and two different regions (subscribers) (This problem was occuring with only one subscriber as well). The merge replication is scheduled to run on the minute. The problem is that we're adding records to the subscribers and occaisionally having the records disappear from the system entirely. Investigations have shown that the records are replicated across the the main database and then deleted. The data in question is a part of a process that creates a main runsheet record with children docket records which in turn have docketdetail records. The runsheets make it across but sometimes the dockets and docket details don't. We're reasonable certain that the reason the records are being deleted is that the main runsheet hasn't been replicated when the children have been copied and so the publisher says "sorry not allowed" deletes them which flows through to the subscribers. One change we've made to try and rectify this is to change the UpdateGenerationsperBatch and DownloadGenerationsPerBatch parameter to 2000. We never have 2000 records altered in one batch and yet the problem has not gone away (seems to have lessened though but it's hard to tell). Should we also alter the upload/download read/write generations per batch parameters. It seems that these won't have an affect.Any ideas?Cheers,MikeT. |
|
|
|
|
|