Re: Need latency help for SQL 2K- Hilary
- From: "Kristy" <forums@xxxxxxxxxxxxxxxx>
- Date: Sun, 4 May 2008 17:46:23 -0400
Also, I don't see that as parameter for that SP. Can you give me an example?
Is it undocumented?
Bascially I don't know how to
determine "where" the problem is occuring to see what I need to fine tune.
And if it is a new batch causing the problem, I'm not sure where I can fix
that given it is probably needed. We have always run batch stuff in the
evening (that HAS to be done) and it has never caused this problem before.
Are there any additional tweaks I can do in the agents to speed up
replication? Anywhere else?
I am now running into the issue of having to ship a copy of the database
overnight once a week, hoping it will catch up during the week, only too
have it expired due to latency. I've done this 3 weeks in a row now and
nothing seems to be helping. It just never catches up.
--Kristy
"Hilary Cotter" <hilary.cotter@xxxxxxxxx> wrote in message
news:2700612F-87C6-4CFD-A0F7-7AB670A35267@xxxxxxxxxxxxxxxx
You can pipe sp_browsereplcmds to a results table (its the @results_table
paramter). I suspect you have a batch operation which is generating a
massive amount of inserts/updates/deletes and replication has to process
all these commands.
"Kristy" <forums@xxxxxxxxxxxxxxxx> wrote in message
news:OE1F5vvqIHA.4884@xxxxxxxxxxxxxxxxxxxxxxx
Anybody have any idea of things I can check with regards to latency on my
replicated servers?
I have a production database with an MDF about 170GB and lots of
continuous activity. All servers are running SQL Server 2K with SP4 on
them. We use Transaction Replication to 2 servers - 1 at the same
location as the production server and 1 in a different state.
For the last few months, I have noticed that during the middle of the
night, nothing seems to be replicating and thus latency builds up. I have
latency jobs in place to record the time to a text file, and thus I can
nail it down to an approximate time that things start going haywire. By
morning, latency is usually 11-12 hours behind and takes all day to catch
up to its normal couple of second latency time. No one will admit to me
what might have changed on the app side or if there is some other issue
going on, so I have to track it down myself.
Any suggestions?
Thanks,
Kristy
.
- References:
- Re: Need latency help for SQL 2K
- From: Hilary Cotter
- Re: Need latency help for SQL 2K
- Prev by Date: Re: Migrating logs to SAN
- Next by Date: Syncronization job
- Previous by thread: Re: Need latency help for SQL 2K
- Next by thread: Re: Merge Replication & Database Mirroring
- Index(es):
Relevant Pages
|
