September 30, 2009 at 1:25 pm
Hi,
Faced failure in replication with below error message.
DELETE Statement Conflicted with COLUMN REFERENCE Constraint
On checking more on this, the delete has happened only on subscriber database. Would the entire replication fail whenever there is a constraint violation on the subscriber?
Please provide your inputs.
Thanks.
M&M
September 30, 2009 at 1:51 pm
Since I know from your previous post on the other forum that this table is not part of the replicated tables but an additional table in the subscriber, you should not get any replication error. I am not sure why you got the error in replication when this is not part of replication.
-Roy
September 30, 2009 at 2:03 pm
Sorry..to be clear.
The table is part of replication. It is one of the articles.
Eg. table A is present in both publisher and subscriber.
And this table A which is on subscriber had a constraint violation with
another table B on subscriber (this table B is not part of replication and also not present in publisher)
M&M
September 30, 2009 at 2:39 pm
So then you have to either drop the constraint on the subscriber or when creating the snapshot specify that the constraint is not for replication.
John Zacharkan
September 30, 2009 at 3:06 pm
If the publisher deletes a row of data on a table where the subscriber has a foreign key constraint, then next time this happens it is going to break again. maybe you should have created the foreign key with Cascade delete or update option
-Roy
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply