Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

SQL Replication - General Network Error

Posted on 2004-04-20
5
219 Views
Last Modified: 2008-01-09
Hi All

During the day when our internet traffic is high we reguarly get 'General Network Error - Check your network documentation' when our server in Asia performs a push replication to America.

Does anyone know why this is, and of any settings we can use, because after about 6 attempts it just gives up, and the syncronise has to be manually started again. Any timeout settings or retry settings we can set?

Replication newbie

Thanks
0
Comment
Question by:gravity100
  • 2
5 Comments
 
LVL 13

Expert Comment

by:danblake
ID: 10868730
Yeah, there are some timeouts you can use...
In the distribution job add the following -QueryTimeOut 0
/*This will keep the replication up, and prevent the distribution from failing*/
You'll find a row in the distribution job which says : distribution -<option> <value>
or modify the default distribution profile in SQL Server (using EM).

I would also highly recommend looking at the bandwidth usage on your firewall.. If this is too high -- you're going to get problems...


The big question is why are you trying to syncronise between Asia and America via Snapshot replication ! (Bit of a problem usually better to use the pre-synced option...)
0
 

Author Comment

by:gravity100
ID: 10869053
Hi

Snapshot replication? I am using transaction replication (push one way only). Not usre what you mean by pre-synced option though? :(. Thanks for the other infor though :)
0
 
LVL 13

Accepted Solution

by:
danblake earned 250 total points
ID: 10869168
Not sure what you mean by pre-synced option though?
Both sites have the data-already and you are not using the snapshot component within the system when sites get out of sync...


Its also possible to verify a batch of commands that have been sent down and get them applied to prevent big delays and increase the replication
have a look at the following other distribution agent profile vars:
-CommitBatchSize
-CommitBatchThreshold
-MaxDeliveredTransactions

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/replsql/replmon_8xk5.asp
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
t-sql need help on t-sql 10 25
SQL Backup Question 2 29
job schedule 8 16
too many installs coming along with SQL 2016? 1 14
For both online and offline retail, the cross-channel business is the most recent pattern in the B2C trade space.
Ever wondered why sometimes your SQL Server is slow or unresponsive with connections spiking up but by the time you go in, all is well? The following article will show you how to install and configure a SQL job that will send you email alerts includ…
Via a live example, show how to extract information from SQL Server on Database, Connection and Server properties
Via a live example, show how to set up a backup for SQL Server using a Maintenance Plan and how to schedule the job into SQL Server Agent.

808 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question