Timeline for How to fix discrepancies between publisher and subscription data?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 2, 2011 at 6:33 | comment | added | Marian | I'll study the possibility of skipping some errors for future. Thank you! | |
| Jun 1, 2011 at 20:25 | comment | added | SqlSandwiches | Check this out - technet.microsoft.com/en-us/library/ms151331.aspx. You could always skip the errors and continue you on your way. | |
| Jun 1, 2011 at 7:11 | comment | added | Marian | I agree with you, I was just searching for other means of fixing this problem. I'll synchronize by hand using tablediff and I'll validate again the replication. One of my colleagues has fixed an older replication conflict by removing some rows, but it seems his operation wasn't complete. Anyway, merge replication is not a choice now, because we don't need data modifications propagated to the publisher. Thanks! | |
| Jun 1, 2011 at 7:06 | vote | accept | Marian | ||
| May 30, 2011 at 21:10 | history | answered | SqlSandwiches | CC BY-SA 3.0 |