Post reply

Replication Server on 100% load

  • July 10, 2009 at 2:01 am

    #212299

    Hi

    since about a week our replication is superslow, as the replicationserver runs on 100% load perma.

    when I run the Profiler, it shows a dozen of entries between 4000 and 7000 CPU (time).

    all of those are related to "sp_MSenumgenerations90" and look like

    declare @p6 bigint

    set @p6=4650626

    exec sys.sp_MSenumgenerations90 4284165,'E61301E8-41F7-48C6-AB18-C4E418CD5C74',0,500,4453137,@p6 output

    select @p6

    < The Sync History mostly shows an error like The merge process was unable to access row metadata at the 'Publisher'. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to write to, or use SQL Profiler to determine the source of the failure. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147200996)
    Get help: http://help/MSSQL_REPL-2147200996

    And if it runs through completely, the job ran about 20 Minutes, where it normally runs max 2 minutes.

    I cant find any useful informations on the web to this and hope you can help me

    I use Microsoft SQL Server 2005 - 9.00.3310.00 Build 3790: Service Pack 2

    on Win2k3 Std all Patches installed

    If you need any Infos, let me know please. I hope that you have some Ideas, as I dont have any more

    Greetings Ben

  • July 22, 2009 at 6:40 am

    #1028259

    In my opinion you should:

    --------------------------

    1) upgrade to sql server service pack 3 and also apply the latest cumulative updates for sp3 as well (cumulative update package 4 for sp3 so far)

    2) perform a re-initialization of the subscription.

  • July 23, 2009 at 9:48 am

    #1029087

    nope didnt work :\

    Getting mad on this crap as there are no damn Infos on the web about this.

    Any more Ideas ?

    Whats this sp_MSenumgenerations90 for? And how can I just stop all Jobs calling this thing?

  • July 24, 2009 at 5:22 am

    #1029564

    Hi, here is a very interesting article:

    http://www.tech-archive.net/Archive/SQL-Server/microsoft.public.sqlserver.replication/2008-07/msg00066.html

  • August 28, 2009 at 7:16 am

    #1046178

    ok i had this error again today on another publication ( or better on 2 of 3 subscribers ) and this time I was able to fix it.

    I saw that

    dbcc checkident (MYTABLE, noreseed) returned

    "Checking identity information: current identity value '133611327', current column value '164663124'." Notice the huge difference.

    So i ran

    dbcc checkident (MYTABLE, reseed) on the 2 Tables of this publication ( on the repl Server )

    what fixed this kind of issue.

    In addition i restartet the Agent service. maybe this had to be, maybe not.

    I hope i can save someone else from having a fuc*** weekend 😉

Viewing 5 posts - 1 through 4 (of 4 total)

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