Timeout Expired... Grrrrr

Question

Timeout Expired... Grrrrr

campbelt101

SSC Veteran

Points: 217
More actions
May 21, 2004 at 12:26 pm

#359814

I am new to replication, but I'm learning fast.

I'm tring to setup a database for Merge replication. The database is about 15GB. That majority of the information is in one table and it has about 89,000,000 rows. When I attempt to setup the first snap shot (which is actually done automatically) the agent reports back "Timeout Expired"
I manually extended this table with a new column (specifying it as a rowcolguid), type uniqueidentifier and it took about 2 hours and 15 minutes to do. I thought if I did it manually, the snap shot agent wouldn't need to.
Any ideas from some quru's. I know there's a least a couple of you guys who are using replication.
BTW... it is a merge replication, running on SQL2000 SP3, Windows 2003, Clustered with 2 nodes Active/Passive and oh yeah... I'm using the EM. Haven't figured out how to do this in T-SQL yet.

Viewing 5 posts - 1 through 4 (of 4 total)

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

TriggerMe SSChampion Points: 11752 More actions · Answer 1

For a Database of that size you are better off doing the snapshot manually!

Backup the Database ship it out to your subscribers, attache the database on the subscriber and then from the Publisher, create your subscription.

15GB over a wire is ludicrous!

Kindest Regards,

campbelt101 SSC Veteran Points: 217 More actions · Answer 2

Yes, it is a little big.

I did finally extend some of the Agent Profile settings and got it to make the snap shot (the problem was with making it, not applying it.)

However, now when the merge agent runs, I get an error message "The agent is suspect. No response within last 10 minutes."

One of the tables in the database has 87034450 records. This table in particular seems to be the issue (go figure). Any idea which setting would need to be modified to stop the "agent is suspect"?

Any help is appreciated. Thanks.

Melissa Naugler Valued Member Points: 67 More actions · Answer 3

15 GB is not that big for merge replication, we are replicating tables in merge replication much larger and they run fine.

To eliminate the query timeout errors, set the -QueryTimeout parameter in the merge agent or the merge profile (looks like you already discovered this)

Agent is suspect is not really a true error (we get these all the time) basically it means that the merge agent did not respond back to your publisher in the time alloted by SQL Enterprise Manager. You can do one of two things with this message 1) ignore it, the merge agent will continue as normal and eventually the agent is suspect error will go away or 2)On the publisher, right click on the merge agents folder, select refresh rates & settings, find the inactivity threshold parameter and set it to a higher number (ours is set to 120 minutes) and you should not see the messages anymore.

campbelt101 SSC Veteran Points: 217 More actions · Answer 4

Melissa... thank you very much for your answer. Thanks for letter me know that I'm on the right track too. Glad to hear you are doing merge replication on similar sized databases.