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 |
|
jcarasick
Starting Member
1 Post |
 Posted - 2010-03-18 : 16:37:56
|
| Using SQLCE 3.5 with IIS websynchronization from .NET winforms app.Tested in a training scenario about five users synched within the same second and seemed to cause deadlock. 3 tables take part in a relationship which I assume creates a transaction maybe causing a deadlock.in the .NET application the OnSyncCompletedCallback method fails due to the deadlock. Now what is reported is the tables affected by deadlock are logged as "conflicts" however other tables that were synched with inserts during the same call were successful. Even though the method as a whole reported failed and caught in a try catch exception.The recommendation in the rep monitor is to synch again which they did and moved the "conflicts" to "inserts".my question(s) are:How can I determine what specifically was in conflict and what was inserted and why (from the subscriber so I can handle it)?Why does the OnSyncCompletedCallback method fail?Does the LastUploadGen change?What can I do to avoid deadlock? |
|
|
|
|
|
Merge Replication Conflicts (deadlock)