Timeline for How to delete duplicate rows in merge replication
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 23, 2015 at 21:54 | vote | accept | tmwoods | ||
| Nov 23, 2015 at 21:52 | comment | added | Kin Shah | Glad that it helped. I have posted as answer to get this out of queue of unanswered questions ! | |
| Nov 23, 2015 at 21:51 | answer | added | Kin Shah | timeline score: 2 | |
| Nov 23, 2015 at 21:48 | history | edited | Kin Shah | CC BY-SA 3.0 |
added 1 character in body; edited tags
|
| Nov 23, 2015 at 21:42 | comment | added | tmwoods | That worked! Awesome, thanks a lot! If you put that as an answer I'll mark it as correct. I scripted the index first (so I wouldn't have to write it out), then dropped it, deleted the row through T-SQL (can't do it through the Edit pane), then re-created the index. | |
| Nov 23, 2015 at 21:21 | comment | added | Kin Shah |
can you try to drop and recreate the index uc1MSmerge_tombstone to see if it fixes the problem ?
|
|
| Nov 23, 2015 at 20:58 | comment | added | tmwoods |
@Kin Yes, the subscriber is a restore of the publisher that may have had KEEP_REPLICATION enabled. I will keep that in mind for future restores, if necessary. Is there a way to correct this now though?
|
|
| Nov 23, 2015 at 20:38 | comment | added | Kin Shah |
By anychance you restored the database with KEEP_REPLICATION ? You rarely hit a dupe in dbo.MSmerge_tombstone unless a database is restored.
|
|
| Nov 23, 2015 at 20:19 | history | asked | tmwoods | CC BY-SA 3.0 |