Hi,
we are facing 'out of syncs' in our Replication (transactional with updateable Subscribers)
I checked MSrepl_errors and did a join to MSREPL_Commands over command ID - hope this is a valid one. In Comnands I found the table (as article) which isn't updated.
I run the sp_browsereplcmds on the xact_seqno ofMSREPL_Commandsand found statements that should update the table - but they didn't. (the column in subscriber is not changed)
The strange thing is, that in the errors table an other table is named as causing an error (a constraint violation of a primary key) - thats confusing for me.
For example:
In errors an error on table A is writen. If a join command_id to commands table. Here TableB as article is listed. Running browserepcmds shows statements updating tableB (which is the subscriber running out of sync)
Sorry, I'm new in replication, so a perhaps silly question:
Behind a seq_no there may be several statements, right?
What happens if the first statement fails? Will the other statements be run on subscriber or will the process just stop?
This issue is realy urgent for us, so I would be realy happy for some advice.
Thanks
Christian