error in replication when update data

  • dear all,

    I have the transactional replication. i have add one column in replicated table. When insert the record, the replication is success, all the data inserted in publisher and subsriber too, including the new column. the problem is when update record in new column, it's not replicated in subsciber..what the causes of this error?

    please share anyone has this cases

  • does anyone knows this case, please give me the clue, i'm stack here bout 3 days..please :crying:

  • which type of transaction replication you used?:-)

  • With the limited information, my suggestion would be to drop the table from the subscriber and the publisher and added it back to replication. You can use stored procedures to accomplish that

  • big thanks for the reply, i use transactional replication. i have drop then add this article in replication. but the same error still appear. i have developed the same replication in other server in the same way. but it's normal. after spent many hours to check over and over again, i found that the owner of database in publisher and subscriber is different. is it the causes of this error?.

  • I don't think the owner is the issue and I can't think of a reason why a different database owner would cause the update to fail but not the insert.

    Can you check the subscribtion database for the update stored procedure there. It should start with sp_MS* and table name.

  • For every table that is being replicated, In your subscriber there will be 3 stored proc. One for update, another for insert and another for delete. When you added the new column, most probably the update stored proc did not get modified. Therefore it does not update in the subscriber for the new column. You could manually recreate the stored sprocs by using sp_scriptpublicationcustomprocs.

    It has been a long time since I have used SQL 2000. So please double check (Test) before doing it in production env

    -Roy

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply