May 15, 2008 at 10:30 pm
We have a SQL server at our head office, we had to update 701052 records, and replication obviously started straight after the update. At the moment it has been 24 hours since we updated the server, but now it seems as if we have double entries in the MSrepl_commands table , can I delete these entries and restart replication. Just by the way , the remote server is at our hosting company and we had problems with our lines, and that seems to be the cause of our initial problems.
Thanks
Arno
May 16, 2008 at 8:24 am
Hi,
Sounds to me like your updates have updated a unique constraint on the publisher. When this happens, replication creates two records, a delete and an insert pair. This is not a problem it is by design, it can cause problems if you are using triggers with PKs!!
This sounds very slow to me.
Perhaps you should try updating the records in batches so that distribtuion can run in batches.
Graeme
May 17, 2008 at 1:37 am
Hi there,
Eventually we found the problem, we found records in the MSRepl_commands table where there was no corresponding article ID in the MSArticles table, we deleted those entries and replication completed witin an hour.
Thanks for the advise, we did learn out of this 🙂
Regards
Arno
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply