Angelo SIlva (3/28/2014)
I know that. I am not checking with that query. I am checking for all records with a query that I create yesterday for the same table.The thing is I don't have access to the customer side to check what is happening there, but the replication is failing from their side when Sql server replicates the information and this happen only to one table from the all 26 tables.
Could this be caused from different data type or definition in the schema?
Do you have any idea.
Thank you
The command succeeded on their side, was written to the transaction log, read and written into the distribution db and subsequently fails to write to your subscriber. So the problem is with the command being applied to your side. Your customer would be unaware of a problem.
If it was a schema difference you would get a different error.
As I said either your local table is out of sync or may be a change to the sql replication topology.
If the table isnt to large you could perform a reinitialisation? Have you looked for commonalities between the missing rows by looking at the failed commands?