Monday, March 26, 2012

Merge Agent takes all the CPU time

The merge Agent takes all the CPU resources and makes no space for other
aplications. When I stope the Server Agent the Server becomes available to
other applications. I start the merge agent again and every thing works fine
.
How can I handle this so I wont have to stop the merge agent each time the
usrs start complaining?
Thanks a lot,
LinaHow often is your merge agent running..? Hourly ..?
Ideally you want to run the merge agent frequently, that way it has a small
amount of data to process and will have less impact on resources
HTH. Ryan
"Lina Manjarres" <LinaManjarres@.discussions.microsoft.com> wrote in message
news:956B2254-A621-4752-BFCD-1DF47151A269@.microsoft.com...
> The merge Agent takes all the CPU resources and makes no space for other
> aplications. When I stope the Server Agent the Server becomes available to
> other applications. I start the merge agent again and every thing works
> fine.
> How can I handle this so I wont have to stop the merge agent each time the
> usrs start complaining?
> Thanks a lot,
> Lina|||Hi Ryan
I have to schedules:
One continuos
and the other one each 5 minutes.
Thank you, Lina
"Ryan" wrote:

> How often is your merge agent running..? Hourly ..?
> Ideally you want to run the merge agent frequently, that way it has a smal
l
> amount of data to process and will have less impact on resources
> --
> HTH. Ryan
> "Lina Manjarres" <LinaManjarres@.discussions.microsoft.com> wrote in messag
e
> news:956B2254-A621-4752-BFCD-1DF47151A269@.microsoft.com...
>
>|||In that case i would suggest running a profiler trace to capture what stored
procedure the merge agent is running when the CPU spike occurs. You may find
it's related to the size of the metadata tables "MSmerge_contents,
MSmerge_genhistory" or the filtering conditions within the publication.
How to troubleshoot SQL Server merge replication problems :-
http://support.microsoft.com/?id=315521
HTH. Ryan
"Lina Manjarres" <LinaManjarres@.discussions.microsoft.com> wrote in message
news:6FD33C8B-468A-4DC4-860C-9E27ED644743@.microsoft.com...
> Hi Ryan
> I have to schedules:
> One continuos
> and the other one each 5 minutes.
> Thank you, Lina
> "Ryan" wrote:
>|||Thanks a lot
Lina
"Ryan" wrote:

> In that case i would suggest running a profiler trace to capture what stor
ed
> procedure the merge agent is running when the CPU spike occurs. You may fi
nd
> it's related to the size of the metadata tables "MSmerge_contents,
> MSmerge_genhistory" or the filtering conditions within the publication.
>
> How to troubleshoot SQL Server merge replication problems :-
> http://support.microsoft.com/?id=315521
>
> --
> HTH. Ryan
> "Lina Manjarres" <LinaManjarres@.discussions.microsoft.com> wrote in messag
e
> news:6FD33C8B-468A-4DC4-860C-9E27ED644743@.microsoft.com...
>
>

No comments:

Post a Comment