Hello,
i set up an pull replication. The first client i setup replication over
LAN and the second client i setup replication over RAS.
Server:
Windows Server 2003
SQL Server 2000
Client PCs:
Windows XP
Pull Replication over MS Syncmanager on demand
Now my problem:
At the first client (setup by LAN) the replication works fine over LAN.
When the client goes outside the office and start the replication over
RAS: It tooks a long time (up to 60 min) to start the replication
process. Sometimes the replication not even starts.
In the syncmanager it looks like the replication hangs.
When the client comes back in the office. The replication works fine?
At the second client (replication setup by RAS) the replication works
fine over RAS.
When the client comes back into the office and start the replication
over LAN: It takes a long time (up to 60 min) to start the replication
process. Sometimes the replication not even starts.
In the syncmanager it looks like the replication hangs.
When the client replicate over RAS. The replication works fine?
The name resolution in my network works good! Is there an cache in the
SQL Server or somebody knows an solution?
Best regards
Tulio Mossoro
looks like a bandwidth problem. Run profiler and see where it is getting
stuck. Also copy a 1 mg file across the RAS link and compare how long this
takes with when you copy it locally.
You can also get an idea of relative bandwidth via ras and compare it with
relative bandwidth via LAN by doing speed tests at
http://www.bandwidth.com/tools/speedTest
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Tulio" <mossorous@.yahoo.de> wrote in message
news:1128676983.748349.239970@.z14g2000cwz.googlegr oups.com...
> Hello,
> i set up an pull replication. The first client i setup replication over
> LAN and the second client i setup replication over RAS.
> Server:
> Windows Server 2003
> SQL Server 2000
> Client PCs:
> Windows XP
> Pull Replication over MS Syncmanager on demand
>
> Now my problem:
> At the first client (setup by LAN) the replication works fine over LAN.
> When the client goes outside the office and start the replication over
> RAS: It tooks a long time (up to 60 min) to start the replication
> process. Sometimes the replication not even starts.
> In the syncmanager it looks like the replication hangs.
> When the client comes back in the office. The replication works fine?
> At the second client (replication setup by RAS) the replication works
> fine over RAS.
> When the client comes back into the office and start the replication
> over LAN: It takes a long time (up to 60 min) to start the replication
> process. Sometimes the replication not even starts.
> In the syncmanager it looks like the replication hangs.
> When the client replicate over RAS. The replication works fine?
> The name resolution in my network works good! Is there an cache in the
> SQL Server or somebody knows an solution?
> Best regards
> Tulio Mossoro
>
|||Hello Hilary,
thanks for your fast answer but this can not be an bandwith problem.
On a few clients it is slow over RAS, on other clients it is slow over
LAN, on other clients it work perfect.
When i set up the replication via RAS then it is slow over LAN. Over RAS
it works perfect.
When i set up replication over LAN it is slow over RAS. Over LAN it
works perfect.
And the best at the end: The first two or three times it works perfect
in any direction. After this the replication gets slow up to not
working.
Is there any SQL Cache that holds the IP?
Thanks a lot in advance
Tulio Mossorous
*** Sent via Developersdex http://www.codecomments.com ***
No comments:
Post a Comment