Home/ Questions/Q 3402692
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-18T05:10:10+00:00

I’m using Merge Replication. The Identity range management is AUTOMATIC I HAVE A TRIGGER

  • 0

I’m using Merge Replication. The Identity range management is AUTOMATIC

I HAVE A TRIGGER ON COMPANIES TABLE WHICH INSERTS ROWS IN SERIALNUMBERSCHEME TABLE which has documentID as identity column

While synchronizing I’m getting below error

A row insert at ‘SERVER\MUMBAI.PROD_SUB’ could not be propagated to ‘SERVER\NEWYORK.PROD’. This failure can be caused by a constraint violation. Explicit value must be specified for identity column in table ‘SerialNumberScheme’ either when IDENTITY_INSERT is set to ON or when a replication user is inserting into a NOT FOR REPLICATION identity column.

Data is inserted properly at subscriber but not replicated at publisher

Any solution/suggesstion?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Sounds like your trigger gets fired when the replication agent applies the updates. Normally the trigger should run only at the publisher (or more precisely, at the site which inserts the original data). Then replication will replicate the effect of the trigger. I think that all you need is to mark the trigger as NOT FOR REPLICATION.

    See Controlling Constraints, Identities, and Triggers with NOT FOR REPLICATION.

    • 0