This sounds like a Hilary question actually, but I will speculate that this
may be a hardware and / or OS issue. With 35 subscribers merging, that's a
lot of data! With NT4 and SQL7, it sounds like this is an older system, so
I'd also be curious to know what sort of hardware you are running and how
long you have been synchronizing subscribers. You may also want to try
shrinking the database if you have not done that in awhile and / or
truncating the log file (after a backup of course). All this data adds to
churn on the harddrive and cpu (my first instinct tells me that you do not
have enough memory and the system is doing a considerable amount of
pagefiling while working with the data). Finally, I would consider
re-creating the publication anew if you can do that without any other
issues.
[quoted text, click to view] "CoSNikO!" <CoSNikO!@discussions.microsoft.com> wrote in message
news:458ECF12-2C46-4B45-9B61-14AFDDE0A818@microsoft.com...
> Earl, i tried some ways to solve this problem and i did not found
> something!
> By configuring sql server to use a percentage of cpu power does not solves
> this problem. Can you help me some more?
>
> "Earl" wrote:
>
>> You do realize you can throttle back what the cpu is using for SQL
>> Server?
>>
>> "CoSNikO!" <CoSNikO!@discussions.microsoft.com> wrote in message
>> news:08AAB530-8AEE-435F-B2EC-F957B92AD302@microsoft.com...
>> > My replication system consists of a Publisher with Windows NT4 w/ SP6a
>> > and
>> > SQL Server 7 w/ SP3 and 35 subscribers, with the same windows and sql
>> > server
>> > versions, beeing synchronized by a schedule.
>> > When i am trying to synchronize a subscription manually my cpu is
>> > running
>> > up
>> > to 100%, blocks were being created continiously in table
>> > MSmerge_genhistory
>> > and the last executed command that i can see is sp_MSmake_generations.
>> > To solve this problem i must restart sql server service and shift the
>> > date
>> > some days back.
>> > Do you have something else?
>> >
>> > Thanks!
>>
>>
>>