Replication QueryTimeout?

  • I have a few transactional replication projects that run over a VPN between sites and I often have to restart the projects because of network errors. I understand that I can modify the distribution agent profile, but can anybody suggest a ball-park figure for QueryTimeout? The default 300 seconds might be a bit short? Has anybody experience of similar problems?

    Steve

  • You can manipulate the batchsize and querytimeout to reduce the errors.

    At work I changed the standard batchsize to 100 and now the replication (on a LAN) won't time out any longer. Perhaps I will increase it later on.

  • Steve,

    If you have continuous replication, set up an additional schedule for the distribution agent. Set it to run in every 5 minutes. This way, in case of the replication job dies, the SQL Agent will restart it in 5 minutes.

    (It's not a solution, it's an addition)

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply