Re: 1 transaction with 800000 commands were delivered
- From: "Donna Lambert" <DonnaLambert@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 22 Apr 2005 14:03:02 -0700
Sorta...
Hilary knows me already!!!
I was in MS support for nearly a decade and have just recently come out into
the "real world." :-)
I've sporadically posted to the newsgroups while I was with
Microsoft...usually under Repl, Security, Clustering, and Notification
Services. But mostly under the managed newsgroups.
Now that I have a little more time on my hands...I thought I'd hang out with
you fine fellows...hope you don't mind!
Donna
"Hassan" wrote:
> Thanks Donna.. So now its u, Hilary and Paul.. Are you a newbie to the group
> ?
>
> "Donna Lambert" <DonnaLambert@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:462631B1-0106-44D4-8DB5-D2A48E6957B2@xxxxxxxxxxxxxxxx
> > Hilary's right here Hassan, but I think the more important thing is to
> talk
> > to your developer about breaking these commands up into multiple
> transactions.
> >
> > You see, if you do an update statement, that let's say, updates all the
> rows
> > in a 40,000 row table, that is 1 Transaction, with 40,000 commands.
> (update
> > orders set ShipCity = 'DonnaTown' for example, will update EVER row in
> orders
> > - 830 rows affected)
> >
> > Depending on what you are actually doing, this could cause replication to
> > SERIOUSLY slow down and even time out.
> >
> > If you can't convince your developer to stop doing LARGE transactions, you
> > could figure out if there are certain insert/update/delete statements that
> > are frequently causing this behavior. Change them to be called from a
> stored
> > proc...then replicate the execution of the stored proc. Your distribution
> > agent will thank you.
> >
> > Donna Lambert
> >
> >
> > "Hilary Cotter" wrote:
> >
> > > batch size and commit batch size are effective when you are applying
> your
> > > snapshot.
> > >
> > > what the 1 transaction with 800000 commands means is that you had an
> insert,
> > > update or delete statement which affected 8000000 rows.
> > >
> > > "Hassan" <fatima_ja@xxxxxxxxxxx> wrote in message
> > > news:%23zNqgA2RFHA.2788@xxxxxxxxxxxxxxxxxxxxxxx
> > > > Seeing this in the status of " 1 transaction with 800000 commands were
> > > > delivered" seemed quite a lot.
> > > >
> > > > I know we have modified our distribution agent profile to 1000 commit
> > > > batchsize and commit threshold.
> > > >
> > > > How does the calculation work ?
> > > >
> > > > Also does it mean that theres some contention especially when we see
> the
> > > > status as " delivering replicated transactions " even after we refresh
> > > > frequently.. ?
> > > >
> > > > Also whats the query issued to see what we see on the right hand pane
> in
> > > > Replication monitor for a publication that shows the agents and last
> > > > action,action time, delivery rate, latency,etc.. ?
> > > >
> > > > Using trans replication
> > > >
> > > > Thanks
> > > >
> > > >
> > >
> > >
> > >
>
>
>
.
- Follow-Ups:
- Re: 1 transaction with 800000 commands were delivered
- From: Paul Ibison
- Re: 1 transaction with 800000 commands were delivered
- From: Hassan
- Re: 1 transaction with 800000 commands were delivered
- From: Hassan
- Re: 1 transaction with 800000 commands were delivered
- References:
- 1 transaction with 800000 commands were delivered
- From: Hassan
- Re: 1 transaction with 800000 commands were delivered
- From: Hilary Cotter
- Re: 1 transaction with 800000 commands were delivered
- From: Donna Lambert
- Re: 1 transaction with 800000 commands were delivered
- From: Hassan
- 1 transaction with 800000 commands were delivered
- Prev by Date: Re: 1 transaction with 800000 commands were delivered
- Next by Date: Re: 1 transaction with 800000 commands were delivered
- Previous by thread: Re: 1 transaction with 800000 commands were delivered
- Next by thread: Re: 1 transaction with 800000 commands were delivered
- Index(es):
Relevant Pages
|