Capture representative load using profiler. Then modify these statements to
simulate 200 users. Make sure you don't run the script in a batch as this
will not simulate a representative load. You will have to stagger the
"Tim Ford" <tim.ford@nospamrubbishin2focus.com> wrote in message
news:%234zgQoG3EHA.2788@TK2MSFTNGP15.phx.gbl...
> Hi Guys,
>
> I have been analysing our merge replication for the past 2 months with
> ongoing performance issues. I have been in constant talks with Microsoft
> regarding performance and bug issues within merge replication and have had
> numerous fixes and hot fixes set to me.
>
> We have found multiple issues within nested views and revaluation of data.
> So the time has come to revaluate some of our database design to resolve
> some potential issues.
>
> MS Support sent me this article
> (
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/mergperf.msp > x) relating to performance tuning and optimization and I would have to say
> what a superb document it is. However I would like to rebuild our test bed
> with automated publisher and subscriber changes to verify bottle neck and
> performance. The original people that wrote the where Damian Castro,
> Alejandro Miguel, Bren Newman.
>
> What I'm looking for is some automated database scripts for hitting the
> publisher server with more that 200 users over a period of time as
> subscribers. Does anyone have any idea where I could get theses scripts
> that
> these guys used or would I have to start writing them now.
>
> Any help would be greatly appreciated.
>
> Thanks, Tim.
>
>