"Methodology" <Methodology@discussions.microsoft.com> wrote in message
news:103B1A4F-FB6F-4AC8-8246-8E7F002FE67F@microsoft.com...
> Hi
>
> Im creating a disaster recovery solution for my company, and accordingly
> have to test SQL replication to death.
>
> With regard to subscriber types, I know that a pull replication creates
> less
> load on the publisher than a push, but as I need to test both types I
> therefore need to strictly measure the difference in system / SQL
> performance
> between the two. Can anyone reccomend what to monitor to accurately
> measure
> the difference on a system between these two subsc types? Im thinking all
> the usual stuff like CPU usage, paging etc and the amount of system
> resources
> the different SQL process use, but is there anything else I could look at
> and
> measure?
>
> Thanks
>
> Alastair Jones
> Methodology Group

"Hilary Cotter" wrote:

> I use the basic CPU, Memory, disk IO, server queue length, disk queue length
> and the basic SQL Counters cache hit ratio, transactions per sec.
>
> If you are using merge its more cpu intensive and all DML has greater
> latency. So watch for locking and durations. Transactional replication adds
> some CPU but not as much as merge. The distribution database is more io
> intensive when its under high load.
>
> There will always high io and locking during snapshot generation.
>
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
>
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
>
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
>
>
> "Methodology" <Methodology@discussions.microsoft.com> wrote in message
> news:103B1A4F-FB6F-4AC8-8246-8E7F002FE67F@microsoft.com...
> > Hi
> >
> > Im creating a disaster recovery solution for my company, and accordingly
> > have to test SQL replication to death.
> >
> > With regard to subscriber types, I know that a pull replication creates
> > less
> > load on the publisher than a push, but as I need to test both types I
> > therefore need to strictly measure the difference in system / SQL
> > performance
> > between the two. Can anyone reccomend what to monitor to accurately
> > measure
> > the difference on a system between these two subsc types? Im thinking all
> > the usual stuff like CPU usage, paging etc and the amount of system
> > resources
> > the different SQL process use, but is there anything else I could look at
> > and
> > measure?
> >
> > Thanks
> >
> > Alastair Jones
> > Methodology Group
>
>