I have a transactional replication between A and B where A replicates its data into B . the schema of A and B are
EXACTLY same. I have a table "t" in both databases which has an
IDENTITY column with name "c" and it is set to be
NOT FOR REPLICATION in both databases. Indeed I have "A.t.c " and "B.t.c " columns. Also I should mentioned that I never do any changes in
B.t table. It should just get the last data from A.t (but because of some reasons I need to have a same schema).
I do the following steps :
1- Add a new row to A.t . (and see the added row in B.t after a few seconds either )
2- update this added row's c2 column (not the c which is the identity and PK column)
3- an exception I receive in Replication Monitor which says I cannot update the
B.t.c column because it is an Identity column!!!... (I checked the related MS's related update stored procedure)...
the question is why it wants to update the Identity column which is not needed indeed!?
View Complete Post