We just added replication to our dev environment then took it off, but SQL left NOT FOR REPLICATION settings on all of the identity columns. Now every other table is failing comparison. Is there a way to ignore this column attribute? Setting it to ignore replication triggers and identity properties didn't work.

Thanks.
spivey24
0

Comments

3 comments

  • spivey24
    Removed
    spivey24
    0
  • icewharf
    spivey24, did you solve this or find some work-around?
    icewharf
    0
  • spivey24
    No, I never found a solution. We ended up taking off replication on the databases we compare and rolling back all of the "not for replication" changes it made, so it became a non-issue.
    spivey24
    0

Add comment

Please sign in to leave a comment.