March 9, 2007 at 12:16 am
A very urgent solution needed I have one main feed Server "A" replicating data to two Servers "B" & "C"
The Distribution agent profiles of Both "B" and "C" are as follows
"B" Distribution Agent Profile
-BcpBatchSize 100000 (default)
-CommitBatchSize 100 (default)
-CommitBatchThreshold 1000 (default)
-HistoryVerboseLevel 1 (default)
-KeepAliveMessageInterval 300 (default)
-LoginTimeOut 15 (default)
-MaxBcpThreads 1 (default)
-MaxDeliveredTransactions 0 (default)
-PollingInterval 10 (default)
-QueryTimeOut 2000
-SkipErrors 2601:2627:20598
-TransactionsPerHistory 100 (default)
"C" Distribution Agent Profile
-BcpBatchSize 100000 (default)
-CommitBatchSize 100 (default)
-CommitBatchThreshold 1000 (default)
-HistoryVerboseLevel 1 (default)
-KeepAliveMessageInterval 300 (default)
-LoginTimeOut 15 (default)
-MaxBcpThreads 1 (default)
-MaxDeliveredTransactions 0 (default)
-PollingInterval 10 (default)
-QueryTimeOut 300
-SkipErrors 2601:2627:20598
-TransactionsPerHistory 100 (default)
The latency for the server "B" is around 500000 & for the Server "C" is around 3000
Can u suggest anything wrong in the agent profile which can cause the Server LAtency to Shoot Up. what is the QueryTimeOut property about. what all things should i check in order to find the cause of the increases latency
thanks in advance
JAcx
March 9, 2007 at 2:15 am
just as an observation I'd look at the subscriber and the network connections, I would imagine latency would not be part of the replication process as such. ( I'm assuming this is std replication ? )
so:-
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply