Merge Replication Initialization-Too many generation batches

External Since: Mar 07, 2006 Posts: 7

I have a SQL 2005-2005 Express Merge replication. Articles with FKs.
Added a new subscriber, when I initialize it, some tables are updated more
190 times. For example, customer table has 100 records, however the
initialization inserts 100 and update 19000 rows. It makes the initialization
too long.
Is this has someting to do the some old snapshot not cleanup or Child and
Parent Generations in Separate Generation Batches?
Any help would be greatly appreciated.

John
Here are some logs:
Enumerating inserts and updates in article 'LogCustomerHeader' (generation
batch 1891)
Downloaded 100 change(s) in 'CustomerList' (100 updates): 253849 total
Enumerating inserts and updates in article 'LogCustomerDetail' (generation
batch 1891)
Downloaded 100 change(s) in 'CustomerList' (100 updates): 253949 total
Downloaded 100 change(s) in 'CustomerList' (100 updates): 254049 total
Downloaded 100 change(s) in 'CustomerList' (100 updates): 254149 total
Downloaded 100 change(s) in 'CustomerList' (100 updates): 254249 total
Downloaded 100 change(s) in 'CustomerList' (100 updates): 254349 total
Downloaded 100 change(s) in 'CustomerList' (100 updates): 254449 total
Downloaded 100 change(s) in 'CustomerList' (100 updates): 254549 total
Downloaded 100 change(s) in 'CustomerList' (100 updates): 254649 total
Downloaded 100 change(s) in 'CustomerList' (100 updates): 254749 total
Enumerating deletes in all articles (generation batch 1901)
Enumerating inserts and updates in article 'LogPosition' (generation batch
1901)
Enumerating inserts and updates in article 'LogPositionOff' (generation
batch 1901)
Enumerating inserts and updates in article 'Email' (generation batch 1901)
Enumerating inserts and updates in article 'User' (generation batch 1901)
Enumerating inserts and updates in article 'CustomerGroup' (generation batch
1901)
Enumerating inserts and updates in article 'CustomerList' (generation batch
1901)
Downloaded 15 change(s) in 'User' (15 updates): 2865 total
Downloaded 46 change(s) in 'CustomerGroup' (46 updates): 8786 total
Downloaded 41 change(s) in 'CustomerList' (41 updates): 254790 total
Downloaded 100 change(s) in 'CustomerList' (100 updates): 254890 total
Downloaded 100 change(s) in 'CustomerList' (100 updates): 254990 total
Enumerating inserts and updates in article 'LogCustomerHeader' (generation
batch 1901)
Downloaded 100 change(s) in 'CustomerList' (100 updates): 255090 total
Enumerating inserts and updates in article 'LogCustomerDetail' (generation
batch 1901)
Downloaded 100 change(s) in 'CustomerList' (100 updates): 255190 total
Downloaded 100 change(s) in 'CustomerList' (100 updates): 255290 total
Downloaded 100 change(s) in 'CustomerList' (100 updates): 255390 total
Downloaded 100 change(s) in 'CustomerList' (100 updates): 255490 total
Downloaded 100 change(s) in 'CustomerList' (100 updates): 255590 total
Downloaded 100 change(s) in 'CustomerList' (100 updates): 255690 total

External Since: Jul 17, 2006 Posts: 274

Hi John,
I understand that when you added a new subscriber to your current SQL
Server 2005-2005 Express merge replication, you found that the
initialization process was too long.
If I have misunderstood, please let me know.

To let me better understand your issue, I would like to know the following
qeustions:
1. How many articles published in your publication database?
2. How much space that the replicated tables have?
3. How many subscribers in your merge replication?
4. How long did the initialize process finish?
5. Could you please mail me (changliw_at_microsoft_dot_com) the replication
logs for further research?

Look forward to your response.

Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications

If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
======================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================