RE: MsMerge_Tombstone
From: Alick [MSFT] (alick@online.microsoft.com)
Date: 03/17/03
- Next message: News Reader: "Find a security breach - forensics"
- Previous message: Jean: "locking out sex sites"
- In reply to: CT: "MsMerge_Tombstone"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: alick@online.microsoft.com (Alick [MSFT]) Date: Mon, 17 Mar 2003 06:08:57 GMT
Hi CT,
It is hard to determine the essential cause of the issue. However, this may
related to Failed Change Conflicts; Conflicts can occur when the
publication's join filtering logic does not match its referential integrity
definitions, the primary key (PK) or foreign key (FK) constraints. This can
occur when the SQL Server relational engine tries to honor a certain
constraint (as defined by the PK-FK relationship between the tables), but
the Merge Agent is honoring the join filter definition between the
articles. The Merge Agent cannot apply the change at the destination
replica because of the table-level constraints, which results in a
conflict. For more information, please refer to the article below:
INF: Understanding Merge Replication Conflict Detection and Resolution
http://support.microsoft.com/default.aspx?scid=KB;EN-US;315514
If the above information does not help, it seems this is a complex problem.
It is difficult to troubleshoot in newsgroup. I would like to suggest that
you contact Microsoft Product Support Services at:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
Hope it helps.
Sincerely,
Alick Ye, MCSD
Product Support Services
Microsoft Corporation
Get Secure! - <www.microsoft.com/security>
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Content-Class: urn:content-classes:message
| From: "CT" <cthemistocli@aw.com.cy>
| Sender: "CT" <cthemistocli@aw.com.cy>
|
| I am using SQL2K SP2. I have four replicas successfully
| synchronising every night. On average every other day
| updating in the database fails due to a referential
| integrity error on table msmerge_tombstone.
|
| The only way I found to solve this problem is to
| synchronise all databases and then delete all data in this
| table through a Transact -SQL query (delete
| msmerge_tombstone).
|
| What am I missing?
|
| Thank you in advance for your help.
|
- Next message: News Reader: "Find a security breach - forensics"
- Previous message: Jean: "locking out sex sites"
- In reply to: CT: "MsMerge_Tombstone"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
