StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1412741
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-09-11T19:05:53.590
FavoriteCount
0
LastActivityDate
2016-03-18T17:59:33.933
LastEditDate
2016-03-18T17:59:33.933
LastEditorUserId
103313
OwnerUserId
103313
ParentId
1357941
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
The problem was that one of the subscribers had old publications and subscriptions in the system tables that were replicated through out the entire system. Which caused the violation of UNIQUE KEY constraint. Once we removed these old entires we were able to restart replication. We were able to identify the valid records in sysmergepublication because we knew the state of this table before the invalid entries were replicated. This <a href="http://social.msdn.microsoft.com/Forums/en-US/sqlreplication/thread/df79fe81-9b5e-4726-88d9-d4d13200564b/?ffpr=0" rel="nofollow noreferrer">forum post</a> shows you how to location invalid publications if you need to. We used the follow sql to check for additional subscription entries: <pre><code>select * from sysmergepublications select * from sysmergesubscriptions where pubid in ( select pubid from sysmergepublications) select * from sysmergesubscriptions where pubid not in ( select pubid from sysmergepublications) </code></pre> Here is the sql that we used to delete the invalid subscriptions: <pre><code>delete from sysmergesubscriptions where pubid not in ( select pubid from sysmergepublications) </code></pre> Note: the code sample above assumes that the sysmergepublication contains only valid publications Alternatively: You can use the <code>EXEC sp_removedbreplication @dbname='<dbname>'</code> to remove replication from the database completely. This command appears to remove all replication triggers from the database.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POThe merge process could not update the list of subscriptions
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDug
UserOwnerUserId
1. USDug
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POThe merge process could not update the list of subscriptions
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.