Hi
We are repeatedly having the trouble of our publisher database becoming unresponsive during network problems.
We have publisher in carribean, distribution agent in canada and subscribers all over. The problem comes when publisher cant deliver to distributor due to network outages.
We are planning on moving the distributor to the carribean ultimately but that will take a while, and our application repeatedly needs to be restarted due to these freezes.
Does anyone know of this problem & possible ways to fix it in the short term (short of changing our replication topology).
is this a bug in replication?
ps.database is merge & transactional pubs. (some tables merge/some trans)
help much apprec,
desAs you say those are network problems, make sure they are persistent.
If so take netadmin help to resolve them.
Are you performing replication over internet?
Refer thru event viewer,SQL error log on both the machines for any assessment.|||Yes, replication is over the internet, so cant really troubleshoot the outages - have been various ddos attacks affecting us.
have found no signs of trouble in error logs/eventvwr - only support saying apps are freezing & claiming is db...guess ill have to take a look at processes for deadlocks while frozen (unfortunately thats usually around 4am! :-(
)...
thanks for advice
des|||I think replication process Internet (on WAN) is slow as compared to over LAN.
What is the level of service pack on all invovled servers?
Review information from this http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/proxy.mspx (http://www.microsoft.com/info/smart404.asp?404;Technet page about configuring ISA and usage of proxy server involved in replication over WAN.
HTH|||all servers win2000 sp4 with sql2000 sp3.
not a WAN, entirely seperate networks.
our long term solution is to move the distributor to the same network as publishers so that publishing dbs dont depend on delivery over internet.
will have to investigate logging the process locks during freezes...
thanks for responses
des|||at last...it happens while I am here to see it - as usual turns out that it is the application feezing, not the database! back to the developers...
thanks satya
des|||Thats the reason, I wanted to refer the logs for any information on this process.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment