Replication "Timeout exceeded" error

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

gosound - 27 Apr 2006 16:45 GMT

Hello everyone,

During our nightly replication we replicate a table SERV from a third party.
This table contains codes for all open and closed orders from the past 2
years. It is around 3 - 3.5 GB of total data. The console starts the first
attempt around 2145 - 2130 and the table runs until around 0100 - 0200.
Every night the first attempt throws an exception with "Timeout exceeded".
This only occurs while we are transferring other large tables simultaneously.
If SERV is running by itself no exception is thrown. The problem is the
timeout is set to expire at 8 hours and the timeout exception is being thrown
between 2 - 4 hours.

Microsoft has a hotfix addressing the exact issue we were experiencing, but
did not seem to work.

KB Article Number(s): 912151, 912731, 912732, 913176, 913177, 913764, 913765,
913766, 913767, 913768, 913772

Language: All (Global)

Platform: i386

Anyone have any ideas?

Reply to this Message

gosound - 27 Apr 2006 16:53 GMT

I am sorry this is on a Win 2003 Server with MS SQL 2000 SP4

Thanks

>Hello everyone,
>
[quoted text clipped - 19 lines]
>
>Anyone have any ideas?

Reply to this Message

Hilary Cotter - 28 Apr 2006 00:31 GMT

what is your commitbatchsize, if its the default I would drop it to 1000.

Also are you using snapshot replication? Any way you could use
transactional?

Signature

Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

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

> Hello everyone,
>
[quoted text clipped - 25 lines]
>
> Anyone have any ideas?

Reply to this Message

gosound - 28 Apr 2006 17:52 GMT

This is a custom process utilizing the SqlBulkCopy component of the .Net 2.0
framework.

Full table replication is required because the data is refreshed once a day
and does not identify new records.

>what is your commitbatchsize, if its the default I would drop it to 1000.
>
[quoted text clipped - 6 lines]
>>
>> Anyone have any ideas?

Reply to this Message