deferred updates in replication

  • I don't have unique constraint and clustered index on my table. still my update is working as Insert/Delete. Any idea?

    please help me!

  • Could you be a little more specific as to the scenario and problem?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • I have transnational replication on PROD. suddenly we are getting consistency errors in replication because of update statement (not for delete and not for insert).

    update command working as Delete/insert pair(deferred update) @ subscriber .

    we made only one change recently , we dropped clustered index on that big table1 as part of troubleshooting prospective. we are getting these error on table1 as delete conflicted with reference constraint

    solution : everyone says "DBCC TRACEON (8207, -1)"

    but Why this is happening all of sudden? we didn't add any new unique constraints on this table1.

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

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