RE: MsMerge_Tombstone
From: Jennifer Lesher [MSFT] (jennle@online.microsoft.com)
Date: 03/14/03
- Next message: Kimberly L. Tripp: "Re: Sql Server Login Restrictions"
- Previous message: Aaron Barkel: "Re: Sql Server Login Restrictions"
- In reply to: CT: "MsMerge_Tombstone"
- Next in thread: Alick [MSFT]: "RE: MsMerge_Tombstone"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: jennle@online.microsoft.com ("Jennifer Lesher [MSFT]") Date: Fri, 14 Mar 2003 20:52:36 GMT
Hi CT,
We're currently researching this and will post more information as soon as
possible.
Please follow the thread in this newsgroup as we will be posting to it, and
not your thread in microsoft.public.sqlserver.replication.
Sincerely,
Jennifer Lesher
MCSE/MCDBA
Microsoft Online Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! - www.microsoft.com/security
|
| 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: Kimberly L. Tripp: "Re: Sql Server Login Restrictions"
- Previous message: Aaron Barkel: "Re: Sql Server Login Restrictions"
- In reply to: CT: "MsMerge_Tombstone"
- Next in thread: Alick [MSFT]: "RE: MsMerge_Tombstone"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
