Problems wih replication (large msmerge_contents)

• TSchwab

  Ten Centuries

  Points: 1357

  More actions

  December 2, 2002 at 2:52 am

  #158697

  Hi there,

  we have a lare replication with about 150 clients running. It worked perfectly for about 6 month. In the last two weeks the duaration of a replication went up from 30 Minutes to more than 12 hours?!?!!

  (Informations to the replication: 1 Database (size approx. 2 GB) 3 publications (1 with every table (112) for push replication only, 1 with 12 tables for pull replication only and 1 with 100 tables for push replication)

  I checked the msmerge_...tables and found about 1.3 million entries in the msmerge_contents and about 2 millions in the msmerge_history. We are using SQL-Server 2000 with SP1. I understand that there is a bug in SP1 if a replication breaks down, unneeded data will be left in the msmerge_histroy table. I deleted the entries with the generation 0 in the history table which do not have a counterpart in msmerge_contents und msmerge_tombstone. Now there are only 90.000 entries in msmerge_history left.

  How can i delete the unneeded data in msmerge_content? I know there is as stored-procedure called sp_metadatacleanup, but if I do this I need everybody to upload his/her datachanges to the server or they will be lost. Is there another way???

  Please, help.

  Well, one more question. Why is the replication working over 6 month with a msmerge_contents table with about 200.000 entries and suddenly it changes to more than a million (5-6 times more) without doing anything to the database?

  Thanks in advance for your help.

  Thorsten

• December 5, 2002 at 8:00 am

  This was removed by the editor as SPAM