Entrar
 
HomeBibliotecaWikiAprenderGaleriaDownloadsSuporte ComunidadeFóruns
Recursos para Profissionais de TI >
> 
> 
Initialization cycles through updates

תשובה Initialization cycles through updates

  • quinta-feira, 2 de agosto de 2012 19:30
     
     
    Entrar para Votar
    0

    We have merge replication with 80 subscriptions to one publication. About 100 table articles of which there are 20 updateable at the subscriber. Retention level is set to 30 days. Pub database is on SQL Server 2008 R2 with all the patches. Subscribers are all Windows 7 PCs with SQL Server 2008 Express running pull subscriptions.  I am seeing this behavior consistently:

    Whenver we add a new subscription or re-initialize a subscription, the system applies the snapshot successfully but then continues on with updates to 5 tables (all download only) 100 updates at a time.  The system cycles through these 5 tables at least 10 to 20 times which makes the length of the job run into over 2 hours with a fast connection. The total number of updates is equal to the recordcount of the table times the number of times it cycles through them

    We are stuck with the 30 day retention time. The tables involved will show in the system table msmerge_history on the subscriber.

    The msmerge_history table in the distribution database seems to be reasonable with only a few thousand rows and the times seem to be recent in that table.

    There are bcp files in the subscriber's folder that have data in them for these tables and the synchronizer announces placing the data in the subscriber using bcp.

    What causes this behavior and how can I fix it?  TIA


     

Todas as Respostas