October 11, 2005 at 9:06 am
Hello folks!!
My replication was working fine until last week.
It started to have a Duration of 4 hours, Delivery Rate of 63,7900 cmds/sec, Latency of 18568296 ms!!! And in most cases fails.
The Error is Timeout, General Network error, Agent is suspect no response within last 10 minutes.
The data base that is being replicated has 260 MBytes.
What can be the problem??
There are typical values for duration/ latency time / delivery rate ???
Thanks,
Cláudia
Cláudia Rego
www.footballbesttips.com
October 12, 2005 at 9:38 am
A little tongue in check but Question #1 would have to be: What changed on your network last week?
Beyond that, what type of replication, across what type/speed link?
Joe
October 14, 2005 at 4:59 am
Hello Joe!
I'm using snapshot replication.
The link is Ethernet with 256 MB/s.
There are typical values for duration/ latency time / delivery rate ???
Thanks
Cláudia
Cláudia Rego
www.footballbesttips.com
October 14, 2005 at 10:33 am
Claudia -
4 hours for 260MB (big B = byte) over what sounds like a 256Kb/sec (little b=bit) connection isn't unreasonable when you take into account overhead, other traffic on the connection, etc. You can really only expect to move about .25MB/sec on a 256Kb connection if you are the only one using the connection at the time.
The timeouts, etc. are problematic, could it be that your connection goes down every so often? According to MS a snapshot should recover/retry a network timeout as long as the timeout is <2 minutes...
Joe
October 18, 2005 at 5:37 am
Hi Joe!
Sometimes at the end of the replication, (my replication takes 47 actions and in the 47th action) the process fails!!
I get an error message:
The process could not bulk copy into table '"SILVAL_DLGLOG_FLOAT"'.
And the error detail:
General network error. Check your network documentation.
(Source: 192.168.193.52 (Data source); Error number: 11)
Why?
Thanks
Cláudia
Cláudia Rego
www.footballbesttips.com
November 3, 2005 at 7:18 am
I understand that it worked previously. Look at the network card make sure you're not set to auto detect. Has anything changed on the network? New routers, switches, etc... Try just copying flat files between the server, elimiate SQL Server from the test.
John Zacharkan
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply