DownloadGenerationsPerBatch

  • Hi Everyone,

    I'm hoping that this is an easy question.  On SQL 2000, SP3 Enterprise Edition in a Cluster Environment, I'm running Merge replication with one updating Subscriber.  The issue I'm having is I'm trying to change the Agent Profile so that the  DownloadGenerationsPerBatch is 1000 instead of the default 100.  After making the change to the profile I stopped and restarted the job so that it is using the newly modified profile yet the downloads are still only moving 100 records per batch.  Does anyone know why it is not using the new setting of 1000?  Am I missing something?  Any and all suggestions or comments are appreciated. 

    Thank you for your time,

    Barbley

  • At a guess I would suggest that restarting the job may have been insufficient to pick up the new settings. Perhaps you need to bounce the SQL Server Agent - just make sure you're allowed the downtime. Though, that might be a bit of a sledgehammer approach too. 


    Regards,

    Steve

    Life without beer is no life at all

    All beer is good, some beers are just better than others

  • Hi Steve,

    Sorry for my delay getting back to you; I didn't realize anyone had responded. I'll see if I can't try that in our Staging/Dev environment.  If it works then I might just be what I need to do in Prod as well.

    Thanks for your suggestion,

    Barbara

  • I just tried this in our Staging/Dev environment and then updated close to 9000 rows in one of our tables yet my results still look like this....

    Downloaded 100 data changes(0 inserts, 100 updates, 0 deletes, 0 conflicts)

    Downloaded 100 data changes(0 inserts, 100 updates, 0 deletes, 0 conflicts)

    Downloaded 100 data changes(0 inserts, 100 updates, 0 deletes, 0 conflicts)

    Downloaded 100 data changes(0 inserts, 100 updates, 0 deletes, 0 conflicts)

    Any other thoughts or opinions as to why I'm not able to get it to update more than 100 records at a time.  I have some major updates to some tables coming up and it is extremely time consuming for the updates to only go 100 at a time when I'm updating close to 100K records.

    I'm open to any ideas - THANKS,

    Barbara

  • Hey Barbara, this time I think I can help you out. Did a little research and it looks to me as though you are on the right track, just changing the wrong flag.

    DownloadReadChangesPerBatch

    DownloadWriteChangesPerBatch

    I changed these two and got the update volumes to change

    You could also look at

    UploadReadChangesPerBatch

    UploadWriteChangesPerBatch

    in order to set how many changes you want going from subscriber to publisher in each batch.

    I believe the DownloadGenerationsPerBatch flag would be useful for where you have multiple different changes to the same pieces of data. Replication is managed by generations of changes so this is what it is probably looking at. With the mass changes you have, they probably all belong to the same generation of changes.


    Regards,

    Steve

    Life without beer is no life at all

    All beer is good, some beers are just better than others

  • Steve,

    I just tested that again after changing those 4 additional parameters and it was successful!!!!  After making the changes to the profile I stop and then restarted the merge job just to make sure it was using the newly modified profile.  Thanks so much for taking the time to look into that further. I really appreciate the help and it is going to make a huge difference for me.

    Thanks again,

    Barbara

  • My pleasure Barabara. I have to know these things sometimes for myh own work, so the time isn't wasted and I've had plenty of help from others, so it's nice to dish some out once in a while.


    Regards,

    Steve

    Life without beer is no life at all

    All beer is good, some beers are just better than others

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

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