I have a replication issue with an instance of sql server 2008 r2 configured as publisher and an instance of sql server 2014 configured as subscriber.
The publisher has two transactional publications, one updatable and one not updatable. Previously I had another sql server 2008 r2 instance acting as subscriber for these two publications and all was fine. I changed the server with a sql server 2014 instance and I registered this new server as subscriber for the publications.
Everything works fine except the thing I'm going to describe you:
Table A is part of the updatable subscription , Table B of the non-updatable.
A website acting on the sql server 2014 instance writes in Table A on the Web server, replication "copies" the inserted row in Table A on the local server. Inserting in this table throws a trigger that updates a text field in Table B (the id field is the same in both Table A and B) that is part of the publication not-updatable. The updated field should be "copied" from the replication service in table B on the web server.
Everything works except this last step and I don't understand why ... If I open table B on publisher server with management studio after the trigger fired, I see the updated field but the update is not transferred to the web server. If I make a manual update of this field with the same query executed by the trigger, the change is correctly replicated online on the subscriber ... If I make a manual insert in Table A on the local publisher server (instead of an entry made by replication after an insert done on the web server- subscriber) the trigger fires and makes the same update on Table B as in the first case but this time the change on the table B on the subscriber is replicated.
It seems that the update made by the trigger is not "visible" to replication and so is not replicated, instead the same update made manually is correctly replicated.
Anyone has an idea on which could be the problem?