Replication failure

  • 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

  • One error could lead to lots of other troubles...Thats my experience though. Did this happen by mistake? Someone deleted in subscriber when it should have been done in Publisher? You could fix it by adding the row back in the subscriber manually.

    Since this is missing only in the subscriber and if there is an update on the publisher for the same deleted row, it will throw error. If you delete the row in publisher, the replication is going to say that it cannot find the row in the replicated DB.

    EDIT : It would be better to post replication question in the replication forum itself.

    -Roy

  • Constraint violation has happened with a table not present in the Publisher database.

    I posted this error on replication forum now.

    M&M

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply